Known Issues in Apache ZooKeeper
Learn about the known issues in ZooKeeper, the impact or changes to the functionality, and the workaround.
- OPSAPS-61188: Zookeeper start fails with custom user as contents inside /var/lib/zookeeper have "zookeeper" as owner instead of the custom user
- In Cloudera Manager the Process Username
for ZooKeeper can be changed from the default
zookeeper
value to any custom value. This configuration change in Cloudera Manager automatically changes the owner of thevar/lib/zookeeper
folder but keepszookeeper
as the owner of any folders or files insidevar/lib/zookeeper
, such asmyid
andversion-2
. As a result ZooKeeper fails to start because it needs to read the snapshots and txnlogs from thevar/lib/zookeeper/version-2
folder when starting. - Zookeeper-client does not use ZooKeeper TLS/SSL automatically
- The command-line tool ‘zookeeper-client’ is installed to all Cloudera Nodes and it can be used to start the default Java command line ZooKeeper client. However even when ZooKeeper TLS/SSL is enabled, the zookeeper-client command connects to localhost:2181, without using TLS/SSL.