Learn about the known issues in ZooKeeper, the impact or changes to the functionality,
and the workaround.
Known issues identified in Cloudera Runtime 7.3.2.20000 SP2
There are no new known issues identified in this release.
Known issues identified in Cloudera Runtime 7.3.2.10000 SP1
- CDPD-121220: OMID TSO fails to start when ZooKeeper plaintext
client port 2181 is disabled
- 7.3.2.10000
- When ZooKeeper plaintext client port 2181 is disabled by setting
zookeeper_enable_client_port to false in
secure/TLS-enabled environments, the OMID TSO (Transaction Status Oracle) role fails to
start if Omid ZooKeeper Secure Client Enabled
omid_enable_secure_zookeeper is set to false. OMID
TSO attempts to connect to ZooKeeper using port 2181, resulting in a connection refused
error Can't contact ZK cluster and prevents the
service from initializing, thereby causing deployment and cluster startup health checks
to time out.
- Configure OMID to use the ZooKeeper secure port:
- In Cloudera Manager, navigate to the OMID
service.
- Go to the Configuration tab.
- Search for Omid ZooKeeper Secure Client Enabled
(
omid_enable_secure_zookeeper).
- Select or set this property to
true to allow OMID to
connect using ZooKeeper port 2182.
- Save changes and restart the OMID service, or restart stale services in
the cluster.
Known issues identified in Cloudera Runtime 7.3.2.100 CHF 1
There are no new known issues in this release.
Known issues identified in Cloudera Runtime 7.3.2
There are no new known issues identified in this release.
Known issues identified before Cloudera Runtime 7.3.2
There are no new known issues from previous releases that affect ZooKeeper in Cloudera Runtime 7.3.2.
