Known issues
Review the list of known issues in Cloudera Flow Management (CFM) 2.1.4.
- JDK limitation
- JDK 8u271, JDK 8u281, and JDK 8u291 may cause socket leak issues in NiFi due to JDK-8245417 and JDK-8256818. Verify the build version of your JDK. Later builds are fixed as described in JDK-8256818.
- JDK error
- JDK 8 version u252 is supported. Any lower version may result in this error when NiFi
starts:
SHA512withRSAandMGF1 Signature not available
- NiFi UI Performance considerations
-
A known issue in Chrome 92.x causes significant slowness in the NiFi UI and may lead to high CPU consumption.
For more information, see the Chrome Known Issues documentation at 1235045.
- KafkaRecordSink puts multiple records in one message
-
All the records are sent as a single Kafka message containing an array of records.
For more information, see NIFI-8326.
- Kudu Client
-
All the records are sent as a single Kafka message containing an array of records.
There is an issue in the Kudu client preventing the creation of a new tables using the NiFi processors. The table needs to exist before NiFi tries to push data into it. You may see this error when this issue arises:
- NiFi Node Connection test failures
-
In CFM 2.1.3, Cloudera Manager includes a new health check feature. The health check alerts users if a NiFi instance is running but disconnected from the NiFi cluster. For this health check to be successful, you must update a Ranger policy. There is a known issue when the NiFi service is running but the NiFi Node(s) report Bad Health due to the NiFi Node Connection test.