Hello @Softwarebyt,  Based on the error posted for @ipson, looks like this matches two NiFi Jiras:  https://issues.apache.org/jira/browse/NIFI-13720 https://issues.apache.org/jira/browse/NIFI-13722  Those fixes get included on CFM 2.1.7.1000: https://docs.cloudera.com/cfm/2.1.7/release-notes/topics/cfm-fixed-issues.html  And CDF for DataHub 7.3.1.0: https://docs.cloudera.com/cdf-datahub/7.3.1/release-notes/topics/cdf-datahub-fixed-issues-flow-management.html  ... View more

Hello @moekraft,  Thanks for reaching our community.  As of now, none of the runtimes supports JDK 21.  But I see there are efforts to include support for it on newer but also on those LTS releases.  Still we do not have information to share about the estimated time, but you can be sure that Cloudera is actively checking on the supported depencies and their EOS to always have a supported version.  You should expect that in the future, before the EOS is met, Cloudera would provide support and communications.  ... View more

Cloudera Support helped me resolved this issue. * The "Bad Health" status displayed in Cloudera Manager was a false-positive monitoring alert. * The Cloudera Manager Service Monitor (SMON) was failing its secure TLS connection handshakes to ZooKeeper due to strict endpoint identification checks introduced in modern Java runtimes (Java 17). Because SMON couldn't pull health metrics, it flagged ZooKeeper as down. * The solution is to configure the JVM argument inside the SMON configuration "Java Configuration Options for Service Monitor (firehose_java_opts)" to bypass the strict certificate hostname checks: `-Djdk.rmi.ssl.client.enableEndpointIdentification=false`.   This cluster is 7.1.9sp1 with 7.13.1 CM. Strangely, another cluster, which has the same cluster version, CM version, and Java version, had no such issue. It was set up six months ago.   Thanks for all the responses.   Best regards, ... View more