Issue #18573 has been updated by Josh Cooper. Status changed from Accepted to Duplicate Target version deleted (3.2.0)
I conflated two separate issues here. The issue Brian reported is that the <b>agent</b> performs multiple DNS lookups (A record) for the puppet master. In my testing, I see 5 lookups for a single agent run where nothing is pluginsync'ed. Note this affects all puppet agents (and has nothing to do with webrick vs passenger). As Patrick mentioned earlier, "The underlying issue I think is captured in #18812", so I'm again marking this as a duplicate. The other issue is that webrick-based puppetmasters perform reverse DNS lookups (PTR record) for each connected socket. I've filed this as #20194. This can also cause pluginsync slowness, but is different that what Brian reported. ---------------------------------------- Refactor #18573: File downloads from pluginsync extremely slow https://projects.puppetlabs.com/issues/18573#change-89122 * Author: Brian Wong * Status: Duplicate * Priority: Normal * Assignee: Brian Wong * Category: * Target version: * Affected Puppet version: 3.0.1 * Keywords: DNS pluginsync * Branch: ---------------------------------------- The [standard library module](http://forge.puppetlabs.com/puppetlabs/stdlib) provides numerous parser functions. It is extremely slow on my client's first puppet agent invocation to download these files. I found that each file downloaded requires a DNS call to the puppet server. I am not sure if it is advantageous, or even possible, to download plugins from multiple sources and therefore believe there should only be one DNS call made regardless of how many files must be downloaded. It is extremely inefficient in the current model. The problem happens only when I am using my Vagrant VMs as Puppet clients though the problem is not limited to these systems. Other systems, notably those running in EC2 (VPC) do not experience the problem. This is because the DNS calls made in EC2 return much more quickly than my local virtual machine setup. My situation is quite similar to [this user experience](https://groups.google.com/forum/?fromgroups=#!topic/puppet-users/Ek4jSO7zC1E) but the solution does not apply to me as it is not the Puppet server performing DNS calls in my case. A `tcpdump` on both server and client during the pluginsync has proven this to me. I am running CentOS 6.3 on both client and server. The puppet version on both client and server is 3.0.1. Please refactor/redesign the DNS calls performed during the pluginsync operation to reduce unnecessary network calls. Thank you. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
