Project

Profile

Help

Issue #1682

Updated by rbarlow about 8 years ago

If you start to sync Puppet Forge, you will notice that the log shows that it is creating a connection for each package that it downloads. 

 <pre> 
 $ pulp-admin puppet repo create --repo-id=forge --feed=http://forge.puppetlabs.com 
 $ time pulp-admin puppet repo sync run --repo-id=forge 
 </pre> 

 You will see many messages like this in the log: 

 <pre> 
 Feb 16 18:04:54 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): forge.puppetlabs.com 
 Feb 16 18:04:55 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): forge.puppetlabs.com 
 Feb 16 18:04:56 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): forge.puppetlabs.com 
 Feb 16 18:04:57 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): forge.puppetlabs.com 
 Feb 16 18:04:58 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): forge.puppetlabs.com 
 Feb 16 18:04:59 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): forge.puppetlabs.com 
 … 
 </pre> 

 I would expect to see it making new connections and then pooling them. 5 connections would look like this in the log: 

 <pre> 
 Feb 16 18:04:54 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (1): forge.puppetlabs.com 
 Feb 16 18:04:55 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (2): forge.puppetlabs.com 
 Feb 16 18:04:56 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (3): forge.puppetlabs.com 
 Feb 16 18:04:57 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (4): forge.puppetlabs.com 
 Feb 16 18:04:58 dev pulp[4674]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (5): forge.puppetlabs.com 
 </pre> 

 If you watch the log during an RPM sync, you will see something similar to the above. 

 The user-facing issue here is that the sync takes a very long time. It is also not particularly friendly to Puppet forge.

Back