Component Upgrade

The component upgrade is performed through Ambari. The process is divided into two stages: installation of the packages available in the new version and execution of the upgrade.

Package Installation

1. In Ambari, on the "Stack and Versions" page, VERSIONS tab, click the INSTALL PACKAGES button of the new version.

   

2. Confirm the package installation.

3. Click the "Show details" link of both versions to view the total number of machines with installed packages.

   
   note

   At this point, even though the new version packages are already installed on the machines, the Cluster still operates with the component binaries of the current version ("CURRENT"). At this stage, any problem with the upgrade will be limited to RPM installation.

• From this point, two options will be available for performing the Upgrade:

  • Express Upgrade: This is the fastest option and all Cluster services will be suspended for the upgrade;

  • Rolling Upgrade: The upgrade is performed without completely stopping the Cluster services.

    
    important

    Before starting the upgrade, make sure that all prerequisites have been met, services are functional, and the Auto Start function is disabled in Ambari.

Express Upgrade Execution

The Express Upgrade is an option that allows upgrading the Cluster components to a new version quickly and safely. However, this option requires a complete stop of all Cluster services.

With all prerequisites met, follow the steps below:

1. Click the UPGRADE button of the new version.

2. Select the "Express" upgrade option.

3. Click "Proceed" to continue.

4. Confirm the operation.

   

5. Monitor the upgrade process and pay attention to the messages and requests displayed on the screen.

   
   warning

   During the Express Upgrade, services are unavailable. The total downtime depends on several factors, such as the number of machines, number of services, network speed, among others.

   
   warning

   If the Apache Hive service is installed, during the upgrade, you will be asked to perform a backup of the Hive Metastore database. This action is necessary to enable recovery in case of failure or version downgrade. Then, back in Ambari, confirm the backup completion to proceed with the upgrade.

   tip

   It is possible to check if the upgraded components are already functional. To do this, click the "all service checks" link. This way, it is possible to identify and fix any problems before the service check stage, performed at the end of the upgrade.

6. Monitor the verification of all upgraded services (Service Check).

   

7. Select one of the following options to complete the upgrade process:

• DOWNGRADE: Allows you to reverse the upgrade process. All components revert to their previous versions.

• FINALIZE LATER: Allows you to finalize the upgrade process at another time, enabling test and validation execution.

• FINALIZE: Finalizes the upgrade process and sets the new version as "CURRENT".

  warning

  If Apache HBase is among the upgraded services, at the end of the upgrade, you will be asked to confirm the deletion of the snapshot created during the process.

8. Select "Finalize" to finalize the upgrade process.

   

9. Click "Proceed" to confirm the finalization of the upgrade process.

Rolling Upgrade Execution

Although it is a slower option, the Rolling Upgrade allows upgrading the Cluster components to a new version without completely interrupting the services. This is possible as long as the services are in high availability or their components operate in a distributed architecture with no single point of coordination and control (No Master).

With all prerequisites met, follow the steps below:

1. Click the UPGRADE button of the new version.

2. Select and confirm the "Rolling Upgrade" option.

3. Confirm the metadata database backup completion.

   
   note

   A series of configurations will be performed automatically during the upgrade.

   note

   At any time, it is possible to suspend the "Rolling Upgrade". To do this, select the "Pause Upgrade" button. This way, it is possible to pause the upgrade to fix any irregularity or revert the operation (rollback).

   

4. Confirm the completion of the manual steps requested.

   
   tip

   It is possible to check if the upgraded components are already functional. To do this, click the "all service checks" link. This way, it is possible to identify and fix any problems before the Service Check stage, performed at the end of the upgrade.

5. Monitor the verification of all upgraded services (Service Check).

6. Select one of the following options to complete the upgrade process:

• DOWNGRADE: Allows you to reverse the upgrade process. All components revert to their previous versions.
• FINALIZE LATER: Allows you to finalize the upgrade process at another time, enabling test and validation execution.
• FINALIZE: Finalizes the upgrade process and sets the new version as "CURRENT".

warning

If Apache HBase is among the upgraded services, at the end of the upgrade, you will be asked to confirm the deletion of the snapshot created during the process.

7. Select "Finalize" to finalize the upgrade process.

8. Click "Proceed" to confirm the finalization of the upgrade process.

Upgrade Conclusion

In the VERSIONS tab of the "Stack and Versions" page, the previous version has been removed and the new version is set as "CURRENT".

Note that the UPGRADE HISTORY tab has been added to the "Stack and Versions" page. This tab shows the cluster upgrade history, including details such as the type of upgrade performed, the previous version, and the new stack version and its services.

Now, in the STACK tab of the "Stack and Versions" page, it is possible to add the new services available in the new TDP version.

Finally, restart the Ambari Server service:

Terminal input

ambari-server restart

important

The Ambari Server restart is necessary for the consolidation of certain changes and configurations.

warning

After finalizing, remember to re-enable the Service Auto Start by selecting the "Service Auto-Start" option in the Ambari side menu and changing the "Auto Start Settings" toggle to "Enabled".