Known Issues in Cloudera Manager 7.9.0
Known issues in Cloudera Manager 7.9.0
- OPSAPS-67152: Cloudera Manager does not allow you to update some configuration parameters.
-
Cloudera Manager does not allow you to set to "0" for the
dfs_access_time_precision
anddfs_namenode_accesstime_precision
configuration parameters.You will not be able to update
dfs_access_time_precision
anddfs_namenode_accesstime_precision
to "0". If you try to enter "0" in these configuration input fields, then the field gets cleared off and results in a validation error: This field is required. - Cloudera bug: OPSAPS-59764: Memory leak in the Cloudera Manager agent while downloading the parcels.
-
When using the M2Crpyto library in the Cloudera Manager agent to download parcels causes a memory leak.
The Cloudera Manager server requires parcels to install a cluster. If any of the URLs of parcels are modified, then the server provides information to all the Cloudera Manager agent processes that are installed on each cluster host.
The Cloudera Manager agent then starts checking for updates regularly by downloading the manifest file that is available under each of the URLs. However, if the URL is invalid or not reachable to download the parcel, then the Cloudera Manager agent shows a 404 error message and the memory of the Cloudera Manager agent process increases due to a memory leak in the file downloader code of the agent.
- Cloudera bug: OPSAPS-65003: Cloudera Manager cluster availability health test reports false alerts
- Cloudera Manager server causes false alerts from the Cloudera Manager cluster availability health test during replacement of the Cloudera Manager server such as an operating system rolling upgrade with VM replacement upgrade. Cloudera Manager cluster availability health test is now disabled by default to avoid false alerts.
- Cloudera bug: OPSAPS-66539: When Ranger Hdfs plugin is enabled in compute cluster from Cloudera Manager, the ranger plugin required system resources like solr and hdfs spool directories path and policy cache directory path are not created.
- User must login to the the node where Namenode roles are running and create the system resource specified in below parameters manually. ranger_audit_hdfs_spool_dir