We're switching back to running as a service, but we observed that the puppet runs tended to cluster together. (We are using foreman also). We used "splay" at boot to randomize the puppet runs, in case we rebooted a lot of systems at the same time, but over time, puppet runs woud cluster together, causing performance issues on the puppet master.
So, we now restart the service a few times a week via cron to re-splay the runs. On Fri, Sep 23, 2011 at 5:42 PM, Brian Gupta <brian.gu...@brandorr.com>wrote: > Over the years many shops have come to start running puppet via cron to > address memory leaks in earlier versions of Ruby, but the official position > was that puppet was meant to be run as a continually running service. > > I am wondering if the official position has changed. On one hand many if > not all of the early Ruby issues have been fixed, on the other, the addition > of mcollective into the mix as a lightweight agent for triggering adhoc > puppet runs, and other tasks somewhat lowers the requirements for puppet to > be run as a service. (Or out of cron for that matter). > > I understand that in cases where old Ruby versions are for whatever reason > mandated the answer may be different. > > Thanks, > Brian > > -- > <http://aws.amazon.com/solutions/solution-providers/brandorr/> > > -- > 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. > -- 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.
