Cloudera Docs

Known Issues in Apache ZooKeeper

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.1.1100 SP3 CHF 6

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.1000 SP3 CHF 5

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.900 SP3 CHF 4

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.706 SP3 CHF 2

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.600 SP3 CHF 1

CDPD-121220: OMID TSO fails to start when ZooKeeper plaintext client port 2181 is disabled
7.3.1.600, 7.3.1.706, 7.3.1.900, 7.3.1.1000, 7.3.1.1100
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:
  1. In Cloudera Manager, navigate to the OMID service.
  2. Go to the Configuration tab.
  3. Search for Omid ZooKeeper Secure Client Enabled (omid_enable_secure_zookeeper).
  4. Select or set this property to true to allow OMID to connect using ZooKeeper port 2182.
  5. Save changes and restart the OMID service, or restart stale services in the cluster.

Known Issues identified in Cloudera Runtime 7.3.1.500 SP3

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.400 SP2

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.300 SP1 CHF 1

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.200 SP1

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1.200CHF 1

There are no new known issues identified in this release.

Known Issues identified in Cloudera Runtime 7.3.1

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.

Workaround:
Manually configure the 2182 port, when zookeeper-client connects to a ZooKeeper cluster.The following is an example of connecting to a specific three-node ZooKeeper cluster using TLS/SSL: 
CLIENT_JVMFLAGS="-Dzookeeper.clientCnxnSocket=org.apache.zookeeper.ClientCnxnSocketNetty -Dzookeeper.ssl.keyStore.location=<path to your configured keystore> -Dzookeeper.ssl.keyStore.password=<the password you configured for the keystore>  -Dzookeeper.ssl.trustStore.location=<path to your configured truststore> -Dzookeeper.ssl.trustStore.password=<the password you configured for the truststore> -Dzookeeper.client.secure=true" zookeeper-client -server <your.zookeeper.server-1>:2182,<your.zookeeper.server-2>:2182,<your.zookeeper.server-3>:2182