Notes and warnings to consider before upgrading to CDP.
Loading Filters
...
7.3.1 7.2.4 7.1.4 7.1.3 7.1.2 7.1.1 7.0.3
6.3.3 6.3.1 6.3.0 6.2.1 6.2.0 6.1.1 6.1.0 6.0.1 6.0.0 5.16 5.15 5.14
5.13
6.3.3 6.3.2 6.2.1 6.2.0
6.1.1 6.1.0 6.0.1 6.0.0 5.16 5.15 5.14 5.13
7.1.6 7.1.5 7.1.4 7.1.3 7.1.2 7.1.1
7.3.1 7.2.4 7.1.4 7.1.3 7.1.2 7.1.1
Minimum Required Role:
Cluster
Administrator (also provided by Full
Administrator ) This feature is not available when using Cloudera
Manager to manage Data Hub clusters.
Note the following before upgrading your clusters:
important
The embedded
PostgreSQL database is NOT supported in production
environments.
The following services are no longer supported as of Enterprise
6.0.0:
Sqoop 2
MapReduce 1
Spark 1.6
Record Service
Running Apache Accumulo on top of CDP Private Cloud Base 7.1.x
cluster is not currently supported. If you try to upgrade to CDP Private Cloud Base 7.1.x, you will be asked to remove the Accumulo
service from your cluster.
Upgrading CDK to Cloudera Runtime 7.1.1 or higher is
only supported from CDK 4.1.0. If you are running an earlier version of CDK, you must
first upgrade to CDK 4.1.0 before upgrading to Cloudera Runtime 7.1.1.
Upgrading Apache HBase from CDH to Cloudera Runtime 7.1.1 gives you are warning in
Cloudera Manager that the Dynamic Jars Directory feature property
hbase.dynamic.jars.dir
is deprecated. You can ignore this warning when
using Apache HBase with HDFS storage on CDP Private Cloud Base . The
hbase.dynamic.jars.dir
property is incompatible with Apache HBase on
cloud deployments using cloud storage.
The minor version of Cloudera Manager you
use to perform the upgrade must be equal to or greater than the
CDH or Cloudera Runtime minor version. Cloudera recommends that
you upgrade to the latest maintenance version of Cloudera Manager
before upgrading your cluster. See Supported Upgrade
Paths . To upgrade Cloudera Manager, see Upgrading Cloudera Manager .
For example:
Supported:
Cloudera Manager 7.1 or higher and Cloudera Runtime
7.0
Cloudera Manager 7.1 and CDH 5.
Cloudera Manager 6.0.0 and CDH 5.14.0
Cloudera Manager 5.14.0 and CDH 5.13.0
Cloudera Manager 5.13.1 and CDH 5.13.3
Not Supported:
Cloudera Manager 5.14.0 and CDH 6.0.0
Cloudera Manager 5.12 and CDH 5.13
Cloudera Manager 6.0.0 and CDH 5.6
note
After upgrading from CDH to CDP, the NodeManager recovery feature is
enabled by default. This means that the
yarn.nodemanager.recovery.enabled
property is set to
true
. Cloudera recommends that you keep the
NodeManager recovery feature enabled. If you set this property to
false
in your CDP cluster and then upgrade to a later
CDP version, the feature will remain disabled.
warning
For upgrades from CDH 5 clusters with Cloudera
Navigator to Cloudera Runtime 7.1.1 (or higher) clusters where
Navigator is to be migrated to Apache Atlas, the cluster must have
Kerberos enabled before upgrading.
warning
For upgrades from CDH 5 clusters with Sentry to
Cloudera Runtime 7.1.1 (or higher) clusters where Sentry privileges are
to be transitioned to Apache Ranger, the cluster must have Kerberos
enabled before upgrading.
note
If the cluster you are upgrading will include Atlas, Ranger, or
both, the upgrade wizard deploys one infrastructure Solr service to
provide a search capability of the audit logs through the Ranger Admin
UI and/or to store and serve Atlas metadata. Cloudera recommends that
you do not use this service for customer workloads to avoid
interference with audit and timeline performance.
important
In Cloudera Runtime 7.1.6 and higher, the way Streams Messaging Manager (SMM) integrates
with Streams Replication Manager (SRM) has changed. SMM can only connect to and monitor an
SRM service that is running in the same cluster as SMM. Monitoring an SRM service that is
running in a cluster that is external to SMM is no longer supported.
Connectivity between the two services is disabled by default after a successful upgrade.
If you want to continue using SMM to monitor SRM, you must reconnect the two services
following the upgrade.