Thanks for the heads up on the exhibitor group, I'll head over there. FYI I more wanted to stop Exhibitor from changing my cfg file than stop it from restarting the node....even if I restart the node by hand if the cfg got changed out from under me I'm still hosed.
Brian On Thu, Nov 29, 2012 at 2:18 PM, Jordan Zimmerman < [email protected]> wrote: > FYI - Exhibitor has its own group: > http://groups.google.com/group/exhibitor-users > > > Is there any way to prevent this not-so-helpful behavior? > You can turn off Instance Restarts for any instance from the Exhibitor > control panel. > > -JZ > > On Nov 29, 2012, at 5:32 AM, Brian Tarbox <[email protected]> wrote: > > > I was performing a manual rolling update of my 3 node cluster when > suddenly > > one of my nodes went into "standalone" mode. I had never seen this mode > > before. > > > > The short answer is that exhibitor was running on a node that I did a > > "zkServer.sh restart" on...and it decided to "help" me by rewriting my > > zoo.cfg. The problem is that it rewrote it as a single node cluster. > > > > Is there any way to prevent this not-so-helpful behavior? > > > > From the netflix exhibitor page: > > "*Each Exhibitor instance monitors the ZooKeeper server running on the > same > > server. If ZooKeeper is not running (due to crash, etc.), Exhibitor will > > rewrite the zoo.cfg file and restart it*." > > > > -- > > http://about.me/BrianTarbox > > -- http://about.me/BrianTarbox
