soabase / exhibitor

ZooKeeper co-process for instance monitoring, backup/recovery, cleanup and visualization.

Home Page:https://groups.google.com/forum/#!topic/exhibitor-users/PVkcd88mk8c

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

zookeeper 3.5 support

b0c1 opened this issue · comments

Hi!
Zookeeper 3.5 dynamic reconfiguration is supported in exhibitor?
Thanks

Not currently. Also, it's a good to time to think about an Exhibitor 3.0. A large portion of Exhibitor's functionality is dealing with the static config of ZK. Now that that's no longer an issue in ZK 3.5 how should Exhibitor work? Please post thoughts for what an Exhibitor 3.0 would look like here.

has there been any update on the development of "Exhibitor 3.0" as i would love to use this :)

Sadly - I opened this project up to anyone who wants to maintain it. Lots of people volunteered but no one seems to be truly taking responsibility.

How would that work? I sent an email to the Exhibitor list when Netflix released the project to me. Lots of people signed up to be committers but nothing's happening.

I'm actually working on publishing my companies intertnal branch to this project. While it doesn't handle this explicit issue it fixes a number of bugs.

I'm sorry it's been quite around here, there isn't much planning or coordination amount committers.

I was wondering if Zookeeper 3.5 dynamic reconfiguration still has not been supported in exhibitor? If it's so, which version of exhibitor supports it?

Thanks

As a note as of 20, May 2019 Zookeeeper 3.5.5 was considered stable and production ready.

Looking at https://zookeeper.apache.org/doc/r3.5.6/zookeeperReconfig.html

It seems that Exhibitor would not change much instead of doing rolling restarts when the configuration changes it can submit the changes to the ensemble to update the config. It could if using S3 backup the configuration there and restore it from there.

However as of 3.5.3 the dynamic configuration is turned off by default over security concerns and has to be explicitly turned on and ACLs setup to use it unless you also enable the skipACL flag or if you run zookeeper in standalone mode it remains static.

I don't see any reason why the current version of Exhibitor would not work for 3.5.x with dynamic reconfig turned off or even enabled. If enabled you'd just not get the not having to restart when changing config when it is enabled.

For anyone trying to run exhibitor with 3.5 here's some things you'll need to do to get it work.

  1. the zookeeper jar is no longer at the root of the home directory and is in the lib directory. I symlinked the jar to the root and this resolved that issue.

  2. Exhibitor uses the 4 letter word commands to check status. in 3.5.3+ the commands need to be whitelisted via 4lw.commands.whitelist. You can set this under the additional config. I used 4lw.commands.whitelist=stat, ruok, reqs, dump, conf, cons, srvr, wchs, wchc, wchp, mntr

  3. 3.5.x added an admin server that runs on port 8080 you will either need to move your exhibitor port, change the port the admin server runs on or turn the admin server off. I chose to move the exhibitor port. Yo change the admin server this can be done by adding either admin.enableServer=false or admin.serverPort=xxxx to the additional config