Hi Jordan, I have one more question on this. As you told me, if zookeeper went down, then exhibitor will start it but suppose if exhibitor went down, then it won't get started up right?
So for this case, we need to write a crontab which keeps on checking the state of exhibitor and restart it if it is down? On Wed, Oct 1, 2014 at 2:18 PM, Jordan Zimmerman <[email protected] > wrote: > Yes > > > On October 1, 2014 at 4:17:00 PM, Check Peck ([email protected]) > wrote: > > Thanks Jordan. One last question, as of now it is showing *OFF* next to > *Automatic > Instance Restarts* button so if I turn it ON on the Exhibitor while > zookeeper is running and taking traffic, then it will be fine? Right? > > On Wed, Oct 1, 2014 at 2:11 PM, Jordan Zimmerman < > [email protected]> wrote: > >> Yes, Exhibitor can be used as a co-process to restart down instances. >> It can also completely manage your ensemble if you like. >> >> -JZ >> >> >> On October 1, 2014 at 3:34:10 PM, Check Peck ([email protected]) >> wrote: >> >> Checking again to see whether anyone know the answer? >> >> On Wed, Sep 24, 2014 at 8:56 AM, Check Peck <[email protected]> >> wrote: >> >>> We have a three node zookeeper cluster and we are also using Exhibitor >>> on top of each zookeeper node. >>> >>> Suppose if any of the zookeeper node goes down or having any errors or >>> issues then is there any way that it can be restarted? >>> >>> I noticed on Exhibitor UI of my zookeeper nodes there is a button for >>> *Automatic >>> Instance Restarts* >>> >>> Does anyone know what does it do? Right now it is in off state. >>> >> >> >
