On Monday, January 21, 2013 1:05:26 PM UTC, Daniel wrote: > > In the larger env it takes about 70 minutes, if it manages to finish at >> all. Initially, as a "quick" test, I was running puppetdb without postgres >> and had to give it 5GB to get it to finish at all (70 mins). With postgres >> 8.4, load on the puppetmaster is significantly reduced, but with 512MB for >> puppetdb (128 + 1MB per node, and then double it for good measure) puppetdb >> still runs out of memory. I set it to 1GB and puppedb just crashed again >> (I've got dumps). Trying with 2GB now. I haven't fiddled with thread >> settings, but my puppet agents aren't deamonized or 'croned', I run them >> using mcollective or manually. So there's only a single puppet agent >> running during this test, on the core nagios server. It seems that there's >> a ruby process taking 100% of one core during this run and nothing else >> "dramatic" seems to be happening (except for puppetdb dying of course). >> >> > Given enough RAM it doesn't sound like PuppetDB is the problem any more, > is that correct? > > The Ruby process is most likely a Puppet Master thread doing the catalog > construction. I think your suffering from a similar problem that we had > recently, where it's not specifically resource collection that's taking up > all the time, it's the Puppet Master turning the exported resources > information into one enormous catalog that takes too long. > > We got around this by bypassing exported resources and querying the > information from PuppetDB directly and using that information in a > template. I suggested the following to another user a few days ago in this > thread: > > https://groups.google.com/forum/#!topic/puppet-users/X6Lm-0_etbA > > Hi Luke,
This sounds like a sensible workaround, I will definitely have a look. I haven't yet had enough time to look at the issue properly, but it seems that this very long time is indeed consumed by catalog construction. Puppetdb fails after this is finished, so it seems that it dies when nagios host tries to report its catalog back. To be honest it's very disappointing that puppet and puppetdb can't handle few thousand exported resources and that workarounds like that are needed. I might need to look at alternatives. Regards, Daniel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/uXWPXZLe_FgJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
