I'm actually curious about how you managed to get so far without needing to move to Mongrel or Passenger...
Pete - am wondering what types of objects you have been running in your config. I'm suspecting really light stuff and probably not a huge amount of it, am I right? Things like file permissions checks, maybe some user/group management? From what I can tell from the code, this sort of stuff would be fairly light on the puppetmaster server, enabling quick compiles of the config... I'm guessing nothing that involves serving a file (as it will require md5 checksums to be run on the puppetmaster), no defines or any other more complex configuration, am I right? At the moment on my systems I'm seeing compile times of around 30 seconds or so, I'm guessing your compile times are much, much quicker. Like a couple of seconds at most perhaps? Personally, I don't consider this insane. I find this an interesting case that could help understanding the complexities of the performance of the puppetmaster compiler. I'm running 0.24.8 and am constantly looking for ways to speed up compilation on the server end (yes, 0.25 is on my radar, waiting for 0.25.1 though...) I'm also interested that you ran into a kernel issue before you ran into the WEBrick 2 connection maximum... Usually the case is that you run into WEBrick dropping connections, not the OS complaining of SYN flooding. Greg On Oct 8, 8:17 am, Pete Emerson <pemer...@gmail.com> wrote: > Either insane ... or ignorant of the fact that one shouldn't push > WEBrick that far. Or maybe both. > > Today I bit the bullet and used the instructions here: > > http://reductivelabs.com/trac/puppet/wiki/UsingPassenger > > to migrate to Passenger. Pretty painless. I tested it on 8141 first, > leaving WEBrick running, then cut over. So far, so good. > > Next up is Puppet 0.25! > > Pete > > On Tue, Oct 6, 2009 at 3:03 PM, Paul Lathrop <paul.lath...@gmail.com> wrote: > > > On Tue, Oct 6, 2009 at 2:10 PM, Pete Emerson <pemer...@gmail.com> wrote: > > >> I'm seeing this in my logs: > > >> kernel: possible SYN flooding on port 8140. Sending cookies. > >> Could not call fileserver.describe: #<Errno::ECONNRESET: Connection > >> reset by peer> > > >> I'm running 0.24 with webrick, and have approximately 180 hosts under it. > > > Respectfully... > > You're insane. It's dumb luck you've gotten this far :-D > > >> I'm guessing that I'm simply hitting the limits of what webrick can do > >> (I'm working on moving to 0.25 and passenger). Is that true? > >> What's the simplest way to alleviate the problem in the meantime? Is > > > Turn off puppet. > > >> there a simple way to migrate to 0.24 and passenger, for example? Or > >> maybe something easier, like configure puppet to run less frequently > >> (or perhaps only on demand)? > > >> Any thoughts appreciated. > > > Most people hit this wall at 30-40 hosts, I made it to about 50. I'm > > shocked you got up to 180. Your only choice is to move to one of the > > scalable options (Mongrel, Passenger, etc.) > > > --Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
