Skip to main content
Version: 1.2.2.0

Upgrade feature

Clemlab introduces UPGRADE FEATURE with OpenSource Data Platform (ODP) 1.2.2.0 version. The upgrade documentation is divide into 3 parts:

  • Upgrade Feature description (this page)

  • Ambari Upgrade

  • ODP Upgrade

    Each article describes the requirements, the upgrade procedure, and key details to care about.

Support for Upgrade​

You must use Apache Ambari 2.7.9.0 with OpenSource Data Platform (ODP) minimum 1.2.1.X to upgrade to 1.2.2.0 stack.

Latest version compatible

Apache Ambari version 2.7.9.0 is the latest compatible with ODP 1.2.2.0. Make sure to use the latest version of Ambari before starting to upgrade.

Getting Ready to Upgrade Ambari and ODP​

Before upgrade Ambari and ODP, your cluster need to be healthy and started. We recommend to review the following checklist

  • For this make sure every services is started.
  • Confirm that you can stop and start are executing successfully for all services.
  • You need to run Ambari Service Check on every services.
  • Clear all alerts, for this you need to understand why they are being generated. Fix as necessary. If you are a Clemlab customer you can request support. there should be no alert.
  • The initiation and termination of time services significantly influence the total upgrade duration, thus it’s beneficial to have this data readily available.
  • Before upgrading, download the necessary software packages. Store them in a local repository or think about using a storage proxy, as all nodes in the cluster will need to download multiple gigabytes.
  • Make sure to create point-in-time backups for all databases that the cluster relies on. This includes, but is not limited to, Ambari, Hive, Ranger, Ranger KMS, and Oozie.
note

For Large cluster, NameNode Startup process time can be very long. You can configure Ambari so it does not timeout when restarting the NameNode. For this you can configure /etc/ambari-server/conf/ambari.properties.

For example if you want to set 15min for timeout you can set:

upgrade.parameter.nn-restart.timeout=900

Once configured you need to restart Ambari service

systemctl restart ambari-server  or ambari-server restart