Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

hdp 3.0 upgradation

Solved Go to solution

hdp 3.0 upgradation

Contributor

Hi Every one,

we are planning to upgrade our kerberised production cluster which is hdp 2.6 to hdp 3.0.

can you please tell me step by step procedures and best practices since i am doing it for first time.

Thanks in advance.

1 ACCEPTED SOLUTION

Accepted Solutions

Re: hdp 3.0 upgradation

New Contributor

Hi

I upgraded my cluster yesterday, following the documentations at:

https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade/content/ambari_upgrade_gu...

Read each and every line, because it is bit different from previous upgrades, few which i noticed:

1. Ambari Metrics System, and SmartSense must be upgraded after first registering the HDP 3.0.x version and installing HDP 3.0.x packages. Please do not attempt to start Ambari Metrics or SmartSense until the HDP 3.0.x upgrade has completed.

2. DO NOT RESTART services after ambari upgrade

3.

  1. If you have configured Ambari to authenticate against an external LDAP or Active Directory, you must re-run
    ambari-server setup-ldap
  2. If you have configured your cluster for Hive, Ranger or Oozie with an external database (Oracle, MySQL or PostgreSQL), you must re-run
    ambari-server setup --jdbc-db and --jdbc-driver

4. There is only one method for upgrading HDP-2.6 to HDP-3.0 with Ambari: Express Upgrade.

An Express Upgrade orchestrates the HDP upgrade in an order that will incur cluster downtime.

5. KDC Admin Credentials

The Ambari Server will add new components as part of the HDP 2.6 to HDP 3.0 upgrade and needs to be configured to save the KDC admin credentials so necessary principals can be created. I used: https://community.hortonworks.com/articles/42927/adding-kdc-administrator-credentials-to-the-ambari....

6. Before upgrading the cluster to HDP 3.0 it’s required to prepare Hive for upgrade. The Hive pre-upgrade tool must be run to prepare the cluster.

2 REPLIES 2

Re: hdp 3.0 upgradation

New Contributor

Hi

I upgraded my cluster yesterday, following the documentations at:

https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-upgrade/content/ambari_upgrade_gu...

Read each and every line, because it is bit different from previous upgrades, few which i noticed:

1. Ambari Metrics System, and SmartSense must be upgraded after first registering the HDP 3.0.x version and installing HDP 3.0.x packages. Please do not attempt to start Ambari Metrics or SmartSense until the HDP 3.0.x upgrade has completed.

2. DO NOT RESTART services after ambari upgrade

3.

  1. If you have configured Ambari to authenticate against an external LDAP or Active Directory, you must re-run
    ambari-server setup-ldap
  2. If you have configured your cluster for Hive, Ranger or Oozie with an external database (Oracle, MySQL or PostgreSQL), you must re-run
    ambari-server setup --jdbc-db and --jdbc-driver

4. There is only one method for upgrading HDP-2.6 to HDP-3.0 with Ambari: Express Upgrade.

An Express Upgrade orchestrates the HDP upgrade in an order that will incur cluster downtime.

5. KDC Admin Credentials

The Ambari Server will add new components as part of the HDP 2.6 to HDP 3.0 upgrade and needs to be configured to save the KDC admin credentials so necessary principals can be created. I used: https://community.hortonworks.com/articles/42927/adding-kdc-administrator-credentials-to-the-ambari....

6. Before upgrading the cluster to HDP 3.0 it’s required to prepare Hive for upgrade. The Hive pre-upgrade tool must be run to prepare the cluster.

Re: hdp 3.0 upgradation

New Contributor

Hi All,

I'm planning to upgrade the cluster from HDP 2.6 to 3.0.Could you please provide me the steps to acheive the same.

Need to know the back up and restore steps in details like Hive ,Ranger and KMS Database before proceeding the upgrade the components.The cluster is not having the HA or Kerberos.

Don't have an account?
Coming from Hortonworks? Activate your account here