Thanks for the answer, but the main question is why puppet need to have 2 puppet runs instead of one in the 2 nd example?
On Wednesday, 15 October 2014 14:11:48 UTC+1, jcbollinger wrote: > > I'm uncertain which differences between the two logs you find > significant. They do appear to have been recorded at different log levels > -- that explains why one has "Updated:" entries and the other does not. > The various packages are managed in different order in the two runs, but > Puppet resource ordering is not guaranteed to be consistent (subject to > several caveats). The two runs show somewhat different sets of resources > being updated, but even if the nodes receive identical catalogs, which > resources are updated will vary depending on which resources need to be > updated. > > Anyway, you cannot parallelize catalog runs. The agent employs a lock > file to ensure that you do not do so. This is because multiple concurrent > runs can conflict with each other. Even if Puppet wanted to parallelize > internally -- and in principle it could do so to some extent -- it is far > trickier than just arbitrarily splitting resources among threads. > Moreover, the gain achievable that way is unclear, but likely to be > variable and small, as most of the time-consuming operations the agent > performs are I/O bound. > > -- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4902b058-3ae9-4b55-94c6-aa01642486ba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
