Please check out the reconfig release document for 3.5.3 beta, in
particular section "Access Control":
https://zookeeper.apache.org/doc/r3.5.3-beta/zookeeperReconfig.html
*"The dynamic configuration is stored in a special znode
ZooDefs.CONFIG_NODE = /zookeeper/config. This node by default is read
Hi,
We were also facing the same issue, this is how we resolved it:
Before starting the ZK server, add the following to zkServer.sh -
"-Dzookeeper.skipACL=yes"
This will skip the ACL authentication and you will be able to use reconfig
command.
Albeit this comes with a risk as you removes all a
I am connecting from ./zkCli.sh and trying to add an server to zookeeper
ensemble
I see i am authenticated on prompt
2018-03-01 11:21:41,716 [myid:localhost:2181] - INFO
[main-SendThread(localhost:2181):ZooKeeperSaslClient@274] - Client will use
DIGEST-MD5 as SASL mechanism.
2018-03-01 11:21:41
