When starting the server using the command:
zkServer start
I get the following response:
JMX enabled by default
Using config: /usr/local/etc/zookeeper/zoo.cfg
Starting zookeeper ... STARTED
awesome, right ? Nope, zookeeper does not stay started… when I run zkServer start again I get the same exact response… forever. I should be getting this, when running the start command again:
MX enabled by default
Using config: /usr/local/etc/zookeeper/zoo.cfg
Starting zookeeper ... STARTED
sh-3.2# zkServer start
JMX enabled by default
Using config: /usr/local/etc/zookeeper/zoo.cfg
Starting zookeeper ... already running as process 8086.
I checked activity monitor and the service is not running either, which I guess it just shows up as ‘Java’.
To install/config zookeeper I did this:
- brew install zookeeper
- sudo easy_install kazoo
- cp /usr/local/etc/zookeeper/zoo_sample.cfg /usr/local/etc/zookeeper/zoo.cfg
- zkServer start
Colleagues doing the same steps do not have this problem…. Any Ideas ?
I build the zookeeper from source and it worked, so something must be hosed with the homebrew zookeeper sometimes. a weird bug.