How about turning off the puppet agent on all the machines, make the change, then turning them back on a few at a time.
Matt On Thu, Aug 29, 2013 at 4:50 PM, <rjbutl...@gmail.com> wrote: > How do I avoid a situation where all of my Linux servers execute a service > restart at the same time upon receiving a new configuration change via > Puppet? I am trying to avoid any possibility that the service would be > unavailable for any length of time. The servers are behind a load > balancer. At least one node needs to remain available. Any idea how I > might configure Puppet to work in this HA environment?**** > > Thank you for your feedback! > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
