Cloudera Docs

Perform express upgrade

You must use the Express Upgrade method to upgrade your cluster from HDP 3.1.5.x to HDP intermediate bits.

  1. Ambari checks that your cluster meets prerequisites. A dialog displays the results:

    • If any required prerequisites are not met, the result displays an error.

      You cannot proceed with the upgrade until you make the appropriate corrections and return to Perform Upgrade again.

    • If any optional prerequisites are not met, the result displays a warning.

      You may proceed with the upgrade.

    • Ambari displays a list of configuration changes that occur during the upgrade.

  2. When the prerequisite checks complete, the upgrade starts. The time required to perform the upgrade depends on many factors. As part of the upgrade process, each component in the cluster restarts in a serial fashion. The stop/start times contribute to the total upgrade time.
  3. The upgrade process includes the following stages. Some stages require that you complete an action during normal operation. If any stage fails, the upgrade stops and prompts you for action.
    Stage Description Action required
    Prepare Upgrade You should stop all apps on YARN queues, and deactivate & kill all running Storm topologies. Perform the actions to prepare for the upgrade.
    Stop Components for High-Level Services This will stop all components for High-Level Services. This includes all master components except those of HDFS, HBase, ZooKeeper and Ranger. None
    Perform Backups This step prompts you to confirm that you have taken proper backups before proceeding. You must acknowledge the prompt for database backups.
    Stop Components for Core Service Stops all components with HDFS, HBase, ZooKeeper and Ranger. None
    Update Target Repository Updates the stack version in Ambari to the target version. None
    Update Service Configs Updates (i.e. transfers or replaces) any configurations that are necessary for the upgrade. None
    Restart Components Restarts all core components such as ZooKeeper, Ranger, HDFS, YARN, MapReduce2 and various Clients (Tez, Pig, Sqoop).

    In an SSO-enabled cluster: If the cookie is lost/session is expired:client should use local login to access the Ambari and proceed further.

    For example: <ambari_host:ambari_port>/#/login/local
    All Service Checks All Service Checks are performed against the cluster. Any service check that fails prompts you to Ignore and Continue, Downgrade or Retry. If you selected the Skip all Service Check failures option, you are only prompted when all Service Checks complete.
    Restart Components Restarts the remaining components such as Oozie, Hive, Spark2 and others. None
    Set Version on All Hosts Sets the HDP version on all hosts to the target HDP version. None
    Finalize Upgrade Pre-Check Checks if any hosts were not upgraded, either because the host was in Maintenance Mode, or one or more components on the host failed to upgrade (and were skipped). Click the list that displays # hosts for details on the hosts (and their components) that are not upgraded. You can Pause Upgrade, delete the hosts and return to finalize.
    Finalize Upgrade The component upgrades are complete. You are presented the option to Finalize, which when selected, completes the upgrade process and saves the cluster state.

    Prompted to Finalize or Finalize Later or Downgrade.
  4. When the upgrade stages complete, you can choose to Finalize the upgrade, or to Finalize Later. Finalizing later gives you a chance to perform more validation on the cluster.
  5. Click Finalize to complete the express upgrade process.