Fixed Issues in Cloudera Manager 7.1.0
This topic lists the issues that have been fixed in Cloudera Manager since the previous release of Cloudera Manager.
- Cloudera Bug: OPSAPS-54084: Cloudera Manager no longer logs sensitive configuration parameters when reading the init file
- Fixed an issue where values of sensitive configuration parameters
might be logged to the
cloudera-scm-server.logwhen they are set using the "-i" argument to Cloudera Manager Server. - Cloudera Bug: OPSAPS-53981: Gracefully handle cyclic dependency exception during configuration validation
- Fixed an issue where setting a Solr service to depend on a Ranger service that already depends on the Solr service would cause a cyclic dependency exception.
- Cloudera Bug: OPSAPS-51606: Null pointer exception when a configuration value is empty
- Fixes a null pointer exception that occurred when a numeric parameter is set to an empty value. Cloudera Manager will use the default value if there is one.
- Cloudera Bug: OPSAPS-54100: Impala Bytes Streamed parameter missing due to profile format change
- Metrics monitoring is now fixed for Impala when using KRPC "streamed bytes" .
- Cloudera Bug: OPSAPS-52988: Application Diagnostic bundle collection does not work for MapReduce jobs.
- Fixed an issue where MapReduce jobs were not being collected in the YARN Application Bundle.
- Cloudera Bug: OPSAPS-52680: Kafka MirrorMaker fails to start if topic whitelist configuration property is not specified
- Kafka MirrorMaker whitelist parameter is now required to ensure that the MirrorMaker process can start.
- Cloudera Bug: OPSAPS-52115: Hive service should not depend on Spark starting with C7
- Hive on Spark related parameters will not appear in the Hive service configuration.
- Cloudera Bug: OPSAPS-53818: Update configuration values to reduce instability from stuck ServerCrashProcedures
- The default value for the
hbase.master.namespace.init.timeoutconfiguration property has been changed to 1800000 ms. - Cloudera Bug: OPSAPS-44250: Add validation for encryption algorithm etc.
- If the
dfs.encrypt.data.transferproperty is enabled and thedfs.encrypt.data.transfer.algorithmproprrty is not set toAES/CTR/NoPaddingthen a warning message is displayed that indicates poor DataNode performance. - Cloudera Bug: OPSAPS-53925: Cloudera Manager agent logs are not showing the correct timezone on the log's timestamp
- The
cloudera-scm-agent.logfile entries now display timestamps with the correct offset based on the timezone of the host.
