Step 12: Complete Post-Upgrade steps for upgrades to CDP Private Cloud Base
Steps to perform after upgrading a cluster.
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
- HBase See Apache HBase post-upgrade tasks
- Apache Hive See Hive Post-Upgrade Tasks.
- Remove the following properties from the Kafka Broker Advanced
Configuration Snippet (Safety Valve) configuration property.
- Save your changes.
- Perform a rolling restart:
- Select the Kafka service.
- Click .
- In the pop-up dialog box, select the options you want and click Rolling Restart.
- Click Close once the command has finished.
- Remove the following properties from the Kafka Broker Advanced Configuration Snippet (Safety Valve) configuration property.
- Kudu See Upgrade Notes for Apache Kudu 1.12 / CDP 7.1
- Stream Messaging Manager See Configure SMM to monitor SRM replications
- Scheduler: If you are using Fair Scheduler, you must migrate to Capacity Scheduler during the upgrade process, and once the upgrade is finished you need to manually fine tune it. For more information, see Manual configuration of scheduler properties.
- Considering logical processors in the
yarn.nodemanager.resource.count-logical-processors-as-coresproperty was not present in CDH 5. In Cloudera Runtime 7.1.1 (and in CDH 6), it is set to
falseby default, meaning that YARN does not consider logical processors in the calculation which can results in a 2x performance hit if Linux Container Executor and CGroups are enabled. To solve this issue, do the following:
- In Cloudera Manager, navigate to .
- Find the YARN Service Advanced Configuration Snippet (Safety Valve) for yarn-site.xml property.
- Add the following
Using this configuration snippet ensures that all nodes that need the configuration receive it. This also ensures different NodeManager groups are consistently configured.
- Restart the NodeManager.
- NodeManager recovery: The default value of the
true. However, if in you source cluster you used safety-valves to set this property to
falseit will stay
falseafter upgrading from CDH 6 to CDP. Cloudera recommends to have this feature enabled and set the
- Log aggregation:: In order to see the history of applications that were
launched before upgrade, do the following:
- In Cloudera Manager, navigate to .
- See the following
- Maximum capacity: Set
yarn.scheduler.capacity.<queuepath>.user-limit-factorto a value that is greater than 1. This configuration will help to grow the queue usage beyond its configured capacity till its maximum capacity configured.
- Ranger PluginsThe following Ranger plugins are not enabled by default after the upgrade. If these services are configured in the cluster, you will need to manually enable the plugins in order for them to use Ranger:
The following Ranger plugins are enabled after an upgrade:
- YARN: If you want to enable the Ranger YARN plugin, you have to migrate the ACLs manually. For more information, see Configure a resource-based policy: YARN.
- Hive on Tez
Ensure, that QuorumSSL (Secure ZooKeeper) is enabled only if QuorumSASL (Server to server SASL authentication) is also enabled. Note, that QuorumSSL is enabled by default if AutoTLS is enabled. If QuorumSSL is enabled without QuorumSASL, then the ZooKeeper cluster can be slow to start due to some known ZooKeeper limitations.
- Solr – See Cloudera Search post-upgrade tasks.
- Sentry – See Sentry to Ranger Permissions.
- Impala – See Apache Impala changes in CDP