Known Issues

Summarizes known issues for this release.

JDK limitation

JDK 8u271, JDK 8u281, and JDK 8u291 may cause socket leak issues in NiFi due to JDK-8245417 and JDK-8256818. Pay attention to the build version of your JDK because some later builds are fixed as described in JDK-8256818.

Workaround: Consider using a more recent version of the JDK like 8u282, or builds of the JDK where the issue is fixed.

ReplaceText with multiple concurrency tasks can result in data corruption

ReplaceText, when scheduled to run with multiple Concurrent Tasks, and using a Replacement Strategy of "Regular Expression" or "Literal Replace" can result in content being corrupted.

The issue is far more likely to occur with multiple Concurrent Tasks, but it may be possible to trigger when using a single Concurrent Task.

To get the fix for this issue, file a support case through the Cloudera portal.

NiFi Registry start issue

When you upgrade CFM, NiFi Registry might fail during the start with the following error message:

Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.b: The content of element 'providers' is not complete. One of '{eventHookProvider, extensionBundlePersistenceProvider}' is expected.

To resolve this issue:

1. Go to the NiFi Registry Advanced Configuration Snippet (Safety Valve) section in Cloudera Manager for staging/providers.xml.
2. Click View as XML and paste the following configuration in the template:

   <property>
   <name>xml.providers.extensionBundlePersistenceProvider.file-bundle-provider.class</name>
   <value>org.apache.nifi.registry.provider.extension.FileSystemBundlePersistenceProvider</value>
   </property>
   <property>
   <name>xml.providers.extensionBundlePersistenceProvider.file-bundle-provider.property.Extension Bundle Storage Directory</name>
   <value>${nifi.registry.working.directory}/extension_bundles</value>
   </property>