[Pkg-puppet-devel] Splitting puppetq?

[micah anderson]

On Fri, 29 Jan 2010 12:41:02 -0800, Russ Allbery <rra at debian.org> wrote:
> micah anderson <micah at riseup.net> writes:
> > Digant C Kasundra <digant at stanford.edu> wrote:
> 
> >> Absolutely.  We commissioned the puppetq work specifically for the
> >> purpose of having storeconfigs running on a different server than the
> >> puppetmasters.  When we turned on storeconfigs on the puppetmasters, we
> >> found that the puppetmasters could no longer handle the load and would
> >> take a long time compiling manifests, sometimes so long that they would
> >> timeout.
> 
> > I'm curious if you recall at what the tipping point for this was. I
> > haven't seen this problem with a couple hundred nodes and one
> > puppetmaster with storeconfigs turned on. I assume I will hit it at some
> > point, but dont know when that will be.
> 
> We have about 500 nodes and we knocked it over dead, but we also have to
> restart our (0.24) Puppet masters every four hours because of the massive
> memory leaks somewhere in Ruby, and it's not clear that other people are
> running into that either.  I'm not sure exactly why we seem to have more
> problems there than others.

I noticed a pretty big improvement with 0.25 and with the rails
backported from BPO. We were having memory leaks with the earlier
version. 

Still using mongrel+nginx, plan to switch to passenger at some point,
our dedicated 2x933mhz PIII with 2gigs of memory seems to be handling
the couple hundred nodes+storeconfigs in mysql fine. I suspect we must
be nearing a tipping point where everything goes downhill, but we
haven't hit it yet.

m
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-puppet-devel/attachments/20100129/78b8db8e/attachment.pgp>