Incompatible Changes in Cloudera Manager 4
Incompatible changes introduced in Cloudera Manager 4.8.0
Cloudera Manager 4.8.0 supports Impala 1.2.1, and does not support Impala 1.1.1 or earlier. This is due to the introduction of the Impala Catalog Server with Impala 1.2.1, which does not work with Impala 1.1. If you upgrade Cloudera Manager to 4.8, you must also upgrade your Impala to version 1.2.1. See http://www.cloudera.com/content/cloudera-content/cloudera-docs/Impala/latest/Installing-and-Using-Impala/ciiu_upgrading.html for instructions.
If you want to continue to use Impala 1.1.1, do not upgrade to Cloudera Manager 4.8.
Incompatible changes introduced in Cloudera Manager 4.6.0
Prior to Cloudera Manager 4.6.0, the Hive Service-level safety valve content (the Hive Service Configuration Safety Valve for hive-site.xml found on the Hive Service Configuration page, under the Service-Wide > Advanced category) was erroneously included in Hive Client Configuration, and was being deployed to /etc/hive/conf/hive-site.xml. It now correctly affects only Hive service roles. Customer who rely on the Service-level safety valve to affect Hive client configuration will need to make sure the correct configuration appears in the Client Safety Valve (Hive Client Configuration Safety Valve for hive-site.xml found under Hive's Gateway role group, under the Advanced category).
Incompatible changes introduced in Cloudera Manager 4.5.0
- Alert Publisher by default sends alert email to "root@localhost", via port 25 (SMTP) on localhost. This can be configured during the wizard setup, or in the configuration settings of the Management Server's Alert Publisher.
- By default, Hive will set hive.warehouse.subdir.inherit.perms to true.
This is a minor change of behavior. If this change is undesired, change the
configuration in the Hive service. This impacts upgrade in the following
- CDH3 cluster to CDH4 cluster using Cloudera Manager 4.5.
- Cloudera Manager upgrade to Cloudera Manager 4.5, where Cloudera Manager is managing a CDH4 cluster.
- Cloudera Manager 4.5 does not support Internet Explorer 8. Users who cannot or do not wish to upgrade to Internet Explorer 9 should not upgrade to Cloudera Manager 4.5.
- The default Java GC options of NameNode, Secondary NameNode, DataNode,
JobTracker, and TaskTracker are now set
-XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=70 -XX:+CMSParallelRemarkEnabled
- Cloudera Manager API v3 (new in Cloudera Manager 4.5) does not support setting a service's roletype configuration, since that has been replaced by the role group. Callers should set the configuration on the appropriate role group instead. Cloudera Manager 4.5 continues to support API v1 and v2. But users who want to upgrade their existing clients to v3 will need to rewrite any roletype configuration calls.
Incompatible changes introduced in Cloudera Manager 4.1.3
Cloudera Manager 4.1.3 supports only version 0.4 of the Cloudera Impala Beta Release. It does not support the earlier beta versions. If you upgrade your Cloudera Manager installation, you must also upgrade Impala to beta version 0.4. If you upgrade Impala to beta version 0.4, you must upgrade Cloudera Manager to 4.1.3.
Incompatible changes introduced in Cloudera Manager 4.1.2
- The alternatives priority of MapReduce 1 (MR1) is now higher than that of MR2 (YARN). This means that the MR1 configuration will take priority by default. In previous releases, if both MR1 and MR2 were installed, MR2 took higher priority. To restore the MR2 to a higher priority, go to the Configuration tab of the YARN service, search for "alternatives" and set the priority to a higher value than the equivalent value for MR1. (By default in Cloudera Manager 4.1.2, YARN is set to 91, and MR1 is set to 92).
- Cloudera Manager 4.1.2 supports only version 0.3 of the Cloudera Impala Beta Release. It does not support the earlier beta versions. If you upgrade your Cloudera Manager installation, you must also upgrade Impala to beta version 0.3. If you upgrade Impala to beta version 0.3, you must upgrade Cloudera Manager to 4.1.2.
|<< Previous: Known Issues Fixed in Cloudera Manager 4.0.1||Next: Cloudera Manager Introduction >>|