Thanks for the response. We're using Posrgres, and the catalog build seems a bit slow, but nothing compared to the client runtime which is where I've been focusing. Your assessment is correct, it is just the nagios server that is extremely slow (~20 mins), there is minimal/no impact to the client machines.
We're at about the 100 hosts, but have closer to 1500 services - maybe we have exceeded what storeconfigs can do then. If that is the case, is there a recommended alternative that isn't manually maintaining config files? It seems like most of the processing time is spent client side and I haven't been able to figure out why. Even doing an md5sum on all of the files from the CLI takes less than 2 seconds. On Mon, Sep 12, 2011 at 3:30 PM, Gabriel Filion <lelu...@gmail.com> wrote: > Hi, > > On 11-09-12 04:43 PM, Justin Lambert wrote: > > We are moving to have our nagios servers generate their nagios configs > > based on what services are installed on specific hosts (as well as the > > hosts registering themselves). What we have found is that our runtimes > > have gone through the roof on this and I'm trying to figure out why > > (summary below from a puppet run). The config pull takes a while, but > > the majority of the time is spent on the client side. Running puppet > > with -d has a large chunk of this time with nothing being updated on the > > screen and one processor core being pegged. We're running 2.6.9 on > > SL6.0 x86_64. > > What db backend are you using for stored configs? > > If you're using the sqlite3 backend, I'd recommend switching to mysql or > postgresql. The sqlite3 backend is mainly there for easing puppet dev, > but it's way too slow for production use.. > > > I'm not sure if I have an unreasonable number of resources and I need to > > do things differently or if I have a problem on my client I need to > > address. Any insight or direction to go down to continue debugging? > > Normally the client run time shouldn't change much with or without > exporting nagios resources, except on the Nagios server (the one > extracting the puppet resources). > > In my experience, exporting native Nagios resources on Nagios clients > and collecting them on the Nagios server doesn't seem to be scaling very > well. But still, it's usable with around 100 hosts and 500 services.. > > -- > Gabriel Filion > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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.
