zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jordan Zimmerman <jor...@jordanzimmerman.com>
Subject Re: Exhibitor rewrote my zoo.cfg with bad configuration
Date Thu, 29 Nov 2012 19:18:39 GMT
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.


On Nov 29, 2012, at 5:32 AM, Brian Tarbox <briantarbox@gmail.com> 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

View raw message