You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@zookeeper.apache.org by Brian Tarbox <br...@gmail.com> on 2012/11/29 14:32:37 UTC
Exhibitor rewrote my zoo.cfg with bad configuration
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
Re: Exhibitor rewrote my zoo.cfg with bad configuration
Posted by Brian Tarbox <br...@gmail.com>.
We use it for data browsing.
On Thu, Nov 29, 2012 at 2:50 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:
> Exhibitor's main raison d'être is to manage zoo.cfg. I'm not sure why
> you'd use Exhibitor if you wanted to manually manage zoo.cfg. However, if
> you turn instance restarts off for all your instances Exhibitor will not
> alter zoo.cfg.
>
> -JZ
>
> -Jordan
>
> On Nov 29, 2012, at 11:47 AM, Brian Tarbox <br...@gmail.com> wrote:
>
> > 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 <
> > jordan@jordanzimmerman.com> 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 <br...@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
> >>
> >>
> >
> >
> > --
> > http://about.me/BrianTarbox
>
>
--
http://about.me/BrianTarbox
Re: Exhibitor rewrote my zoo.cfg with bad configuration
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
Exhibitor's main raison d'être is to manage zoo.cfg. I'm not sure why you'd use Exhibitor if you wanted to manually manage zoo.cfg. However, if you turn instance restarts off for all your instances Exhibitor will not alter zoo.cfg.
-JZ
-Jordan
On Nov 29, 2012, at 11:47 AM, Brian Tarbox <br...@gmail.com> wrote:
> 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 <
> jordan@jordanzimmerman.com> 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 <br...@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
>>
>>
>
>
> --
> http://about.me/BrianTarbox
Re: Exhibitor rewrote my zoo.cfg with bad configuration
Posted by Brian Tarbox <br...@gmail.com>.
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 <
jordan@jordanzimmerman.com> 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 <br...@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
>
>
--
http://about.me/BrianTarbox
Re: Exhibitor rewrote my zoo.cfg with bad configuration
Posted by Jordan Zimmerman <jo...@jordanzimmerman.com>.
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 <br...@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