Known Issues

Summary of known issues for this release.

• Issue:

  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.

• Issue:

  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.

  Workaround:

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

• Issue:

  SAM app with storm-druid sink throws exception.

  Workaround:

  There is no workaround for this issue.

• Issue:

  Restarting Stream Analytics Manager may occasionally fail.

  Workaround:

  In most cases hitting a Retry button solves the issue. If retry does not solve and issue is Downloading mysql jdbc driver failed, the particular file marked in the logs should be removed on that node in /tmp. After that the installation can be continued.

• Issue:

  Stream Analytics Manager installation may occasionally time out. This is caused by the same root cause as the restart failure issue.

  Workaround:

  Delete the mysql jar from the Stream Analytics Manager host /tmp folder, and retry after the timeout.

• Issue:

  When you upgrade HDF from an older version (pre 3.5.0.0) on HDP, 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.

  Workaround:

  To resolve this issue, add the following configuration to Advanced nifi-registry-providers-env in Ambari:

  <extensionBundlePersistenceProvider>
          <class>org.apache.nifi.registry.provider.extension.FileSystemBundlePersistenceProvider</class>
          <property name="Extension Bundle Storage Directory">{{nifi_registry_internal_dir}}/extension_bundles</property>
  </extensionBundlePersistenceProvider>

• Issue:

  Install or upgrade of HDF fails as the URL for HDP-UTILS, in the mpack, is not correct.

  Workaround: - must be replaced with / after the HDP-UTILS string. For example, replace https://archive.cloudera.com/p/HDP-UTILS-1.1.0.22/repos/centos7 with https://archive.cloudera.com/p/HDP-UTILS/1.1.0.22/repos/centos7.

• Issue:

  The default Ambari reporting task in NiFi is not configured correctly and the NiFi metrics are not properly displayed in Ambari even though there is no reported error.

  Workaround:

  In the reporting task configuration, change the Application ID property to an uppercase value: NIFI. For example:

  

• TSB-497: CVE-2021-27905: Apache Solr SSRF vulnerability with the Replication handler

  The Apache Solr ReplicationHandler (normally registered at "/replication" under a Solr core) has a "masterUrl" (also "leaderUrl" alias) parameter. The “masterUrl” parameter is used to designate another ReplicationHandler on another Solr core to replicate index data into the local core. To help prevent the CVE-2021-27905 SSRF vulnerability, Solr should check these parameters against a similar configuration used for the "shards" parameter.

  For the latest update on this issue, see the corresponding Knowledge article: TSB 2021-497: CVE-2021-27905: Apache Solr SSRF vulnerability with the Replication handler