Learn about the known issues in Phoenix, the impact or changes to the functionality,
and the workaround.
Known issues identified in Cloudera Runtime 7.3.2.10000 SP1
- OMID configuration issue after upgrading to Cloudera Runtime
7.3.2.
- 7.3.2.10000
- After upgrading from Cloudera Runtime 7.1.9 or
7.3.2.0 to 7.3.2.10000, the OMID service is configured incorrectly. If HBase is
configured to use the unsecure ZooKeeper port (HBase ZooKeeper Secure Client
Enabled is set to
false), creating an OMID transactional
table from phoenix-sqlline fails because the required TLS configuration
is not sent to ZooKeeper.
- Use one of the following workarounds:
- Workaround 1: On the upgraded cluster, set the
OMID configuration property Enable TLS/SSL for Omid tso server
(
ssl_enabled) to false. Restart OMID and all
dependent services with Re-deploy client configuration
enabled.
- Workaround 2: On the upgraded cluster, set the
HBase configuration property HBase ZooKeeper Secure Client
Enabled (
hbase.zookeeper.property.client.secure) to
true. Restart HBase and all dependent services with
Re-deploy client configuration enabled.
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 known issues carried forward that affect Phoenix in Cloudera Runtime 7.3.2.
