Not sure what his issue was but in my organization we had one puppet master with mod_passenger and puppet 2.6.3 running fine with 200 clients in a VM. We expanded to a 2 node cluster, with the original puppet master serving as the master for the secondaries. The secondaries have an F5 infront of them with no session persistence round robin and a health monitor to know if one of the masters had gone down.
On Jan 11, 9:44 pm, donavan <dona...@desinc.net> wrote: > On Jan 11, 2:45 pm, DaveQB <david.w...@drdstudios.com> wrote: > > > We had trouble scaling with 400+ nodes. Puppet server is a VM on an > > ESX cluster with 3.5GB of ram and 1.5GB of swap but would regularly > > kick in OOM which would kill off most if not all of the 10 > > puppetmaster instances. > > This is very surprising to me. Is this .24 or .25 per chance serving > large files via the File resource per chance? There were some big > memory improvements in File handling around 2.6.0. > > Using 2.6.x, Ruby 1.8.7, Apache 2.2 and passenger I'd expect around > 100-200mb usage per process. Even that seems a bit high to me, though > I don't know what's shared and whats resident off hand. -- 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.
