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

Known Issues Fixed in Cloudera Manager 4.8.3

Sensitive configuration values exposed in Cloudera Manager

Certain configuration values that are stored in Cloudera Manager are considered sensitive, such as database passwords. These configuration values should be inaccessible to non-administrator users, and this is enforced in the Cloudera Manager Administration Console. However, these configuration values are not redacted when they are read through the API, possibly making them accessible to users who should not have such access.

Gateway role configurations not respected when deploying client configurations

Gateway configurations set for gateway role groups other than the default one or at the role level were not being respected.

Insufficient password hashing in Cloudera Manager

In versions of Cloudera Manager earlier than 4.8.3, user passwords are only hashed once. Passwords should be hashed multiple times to increase the cost of dictionary based attacks, where an attacker tries many candidate passwords to find a match. The issue only affects user accounts that are stored in the Cloudera Manager database. User accounts that are managed externally (for example, with LDAP or Active Directory) are not affected.

In addition, because of this issue, Cloudera Manager 4.8.3 cannot be upgraded to Cloudera Manager 5.0.0. Cloudera Manager 4.8.3 must be upgraded to 5.0.1 or later.

Workaround: None. Upgrade to Cloudera Manager 4.8.3 or 5.0.1.

Some Impala queries do not appear on the Cloudera Manager Impala Queries page

Many Impala queries run on Impala version 1.3.1 will not show on the Cloudera Manager Impala Queries Page.

Workaround: None. Upgrade to Cloudera Manager 4.8.3.

Gateway role configs not respected when deploying client configs

Gateway role configurations are not respected when deploying client configurations.

Workaround: None. Upgrade to Cloudera Manager 4.8.3

Error if attempting to watch more than 1024 directories in Reports Manager

Reports Manager does not allow more than 1024 directories to be watched when configuring directory-based usage reports.

Workaround: None. Upgrade to Cloudera Manager 4.8.3.

Log messages beginning with a newline character cause log searching to fail

In previous releases of Cloudera Manager, log messages beginning with a newline character would cause log searching to fail, and increase CPU utilization for the Cloudera Manager Agent.

Workaround: None. Upgrade to Cloudera Manager 4.8.3.

Filtering on host does not return a result even if the job shows the host

In the Cloudera Manager UI, clicking Activities > MapReduce Jobs, selecting a MapReduce job, and filtering on "host" does not return a result even if the job shows the host.

Workaround: None. Upgrade to Cloudera Manager 4.8.3.

Cluster Installation automatically aborts with Google Chrome and Cloudera Manager 4.8.2

Cluster Installation automatically aborts with Google Chrome and Cloudera Manager 4.8.2.

Workaround: None. Upgrade to Cloudera Manager 4.8.3.

Documentation reflects requirement to enable at least Level 1 encryption before enabling Kerberos authentication

The Cloudera Manager manual Configuring Hadoop Security with Cloudera Manager now indicates that before enabling Kerberos authentication you should first enable at least Level 1 encryption.