This is the documentation for Cloudera Manager 4.8.5.
Documentation for other versions is available at Cloudera Documentation.

Known Issues Fixed in Cloudera Manager 4.6.1

— Upgrade to 4.6.0 with HA enabled will cause HDFS restarts/failovers to fail.

When upgrading to 4.6.0 with HDFS High Availability enabled, if the service-rpc port is not already configured, the upgrade will change the port value to 8022, which will cause HDFS failover or restart to fail.

Severity: High

Resolution: Fixed in Cloudera Manager 4.6.1. Upgrading from 4.5 to 4.6.1 works as expected.

Workaround: For each NameNode, add an entry to the hdfs-site.xml service-wide safety valve that specifies an empty entry for the servicerpc-address:
<property>
   <name>dfs.namenode.servicerpc-address.{nameservice_name}.{namenode_id}</name>
   <value></value>  
</property>

Then restart the HDFS service.

To find Nameservice names and their corresponding NameNode identities, look in the hdfs-site.xml of a NameNode by looking at a property of the form dfs.ha.namenodes.{nameservice_name}. You can find the hdfs-site.xml of a running NameNode by clicking on the NameNode, clicking on the Processes tab, clicking "Show", then clicking on the file name. 

— Parcels are removed from all nodes when removed from the server's parcel repo.

Removing parcels from Cloudera Manager server's parcel-repo will remove them from ALL nodes to which they've been distributed.

Severity: Med

Resolution: Fixed in Cloudera Manager 4.6.1.

Workaround: None.

— Setting up Federation may cause the JournalNode to be reformatted.

When adding a Nameservice to an HDFS service that already has a Nameservice that is using JournalNodes, the new NameNodes should be configured (via the safety valve) with a QuorumJournal URL that has a different journal name from the original nameservice. If the journal name is not changed, the JournalNode's directory will be reformatted.

Severity: High

Resolution: Fixed in Cloudera Manager 4.6.1— the NameNode format step will fail if the new Nameservice is configured to use the same journal name as the existing Nameservice, and no reformat will occur.

— Agent fails to start with error regarding postgresql_jar.

After an upgrade from Cloudera Manager 4.5, the agent may fail to start with error message UnboundLocalError: local variable 'postgresql_jar' referenced before assignment if /etc/default/cloudera-scm-agent has an export for CLOUDERA_POSTGRESQL_JDBC_JAR.

This line will only be present if any part of the file was modified while CM4.5 was installed or if it was manually added.

Severity: Med

Resolution: Fixed in Cloudera Manager 4.6.1.

Workaround: Remove the export line for CLOUDERA_POSTGRESQL_JDBC_JAR from /etc/default/cloudera-scm-agent on all hosts.

— After JobTracker failover, Activity Monitor cannot collect job statistics for new jobs.

If JobTracker High Availability is enabled and a failover occurs, the Activity Monitor may not be able to collect complete or consistent information about attempts for any new jobs running on the JobTracker. Currently there is no workaround but to restart the MapReduce service.

Severity: Med

Resolution: Fixed in Cloudera Manager 4.6.1.

Workaround: Restart the MapReduce service.

— Hadoop User Group LDAP password configurations are shown in clear text.

Under the HDFS service configuration settings (in the Service-Wide > Security category), the Hadoop User Group Mapping LDAP SSL Keystore Password and Hadoop User Group Mapping LDAP Bind User Password are shown in clear text rather than being masked.

Severity: Med

Resolution: Fixed in Cloudera Manager 4.6.1.

Workaround: None.