Puppetmaster 3.7.3 startup times when many environments exist
87 views
Skip to first unread message
hecto...@gmail.com
Nov 12, 2014, 11:41:38 AM11/12/14
to puppet...@googlegroups.com
Hello,
My problem: it takes 2 minutes and 14 seconds for the puppetmaster to start (and it uses 100% cpu). It also seems to take way longer if spawned by Apache/passenger.
We run a larger-than-average Puppet setup, with 1892 different puppet environments, each of them different from each other.
Traditionally we have not used "environments", but rather played with the "modulepath" variable to simulate them (since before they were implemented as such this was the way to do it).
Now I am trying to enable "environments" the proper way, by setting environmentpath etc.
Strace shows that the puppetmaster will try to read every single environment directory and environment.conf file during startup and it is obviously setting up some underlying configuration as it takes a considerable large amount of time for every environment.
I don't know how far in 3.x this goes since we never cared to test them.
My questions:
* Any idea how to workaround it (other than keeping our modulepath-based configuration, which works well)
* Assuming this is a just a "warm up" time, will a low "environment_timeout" setting cause the retriggering of such slow operations as the ones happening during the puppetmaster start on a regular basis?
Even as a one-time warm-up time this is not acceptable for us so I guess we will keep using our current way, even with the deprecation warnings. Note I think the new "environments"-way makes totally sense and the model fits better for large diverse setups like ours. It just does not work well.
If any developer is watching this list, it would be good to now if this can be considered a bug (I can open a ticket), or is part of the environment's "feature". Regards!
Hector
My problem: it takes 2 minutes and 14 seconds for the puppetmaster to start (and it uses 100% cpu). It also seems to take way longer if spawned by Apache/passenger.
We run a larger-than-average Puppet setup, with 1892 different puppet environments, each of them different from each other.
Traditionally we have not used "environments", but rather played with the "modulepath" variable to simulate them (since before they were implemented as such this was the way to do it).
Now I am trying to enable "environments" the proper way, by setting environmentpath etc.
Strace shows that the puppetmaster will try to read every single environment directory and environment.conf file during startup and it is obviously setting up some underlying configuration as it takes a considerable large amount of time for every environment.
I don't know how far in 3.x this goes since we never cared to test them.
My questions:
* Any idea how to workaround it (other than keeping our modulepath-based configuration, which works well)
* Assuming this is a just a "warm up" time, will a low "environment_timeout" setting cause the retriggering of such slow operations as the ones happening during the puppetmaster start on a regular basis?
Even as a one-time warm-up time this is not acceptable for us so I guess we will keep using our current way, even with the deprecation warnings. Note I think the new "environments"-way makes totally sense and the model fits better for large diverse setups like ours. It just does not work well.
If any developer is watching this list, it would be good to now if this can be considered a bug (I can open a ticket), or is part of the environment's "feature". Regards!
Hector
Eric Sorenson
Nov 12, 2014, 2:01:39 PM11/12/14
to puppet...@googlegroups.com
This sounds like it's related to the following bug: https://tickets.puppetlabs.com/browse/PUP-3389
Can you please add any troubleshooting info you have onto that ticket? We are aware of the issue and are interested in characterizing it to build a fix.
Thanks!
hecto...@gmail.com
Nov 13, 2014, 6:06:48 AM11/13/14
to puppet...@googlegroups.com
Thank you, I will follow up on the ticket.
Reply all
Reply to author
Forward
0 new messages