Your suggested change has been received. Thank you.

close

Suggest A Change

https://thales.na.market.dpondemand.io/docs/dpod/services/kmo….

back

Upgrade Existing Thales Data Platform

Apply 3.1.5.1 Patch

search

Apply 3.1.5.1 Patch

This document describes how to upgrade TDP from version 3.1.5 to version 3.1.5.1. If your TDP has any prior version please update it first to 3.1.5.

Preparing for the Patch Upgrade

The first stage is to download the patch script, patch VDF file and the patch tarball and prepare the script for Patch Upgrade.

Please follow the steps below for each of the nodes of the TDP cluster:

  1. Copy the patch upgrade script patch_3_1_5_1.sh obtained from Thales Customer Support to /var/tmp/ on this node.

  2. Give execution permission to the upgrade script patch_3_1_5_1.sh on this node.

    1
    chmod +x /var/tmp/patch_3_1_5_1.sh
    
  3. Copy the tar file patch_3.1.5.1-316.tar.gz obtained from Thales Customer Support to this node. This can be also placed on a web server that is external to the TDP cluster nodes with in the same network.

  4. Run the upgrade script with a -d parameter and the path of tar file patch_3.1.5.1-316.tar.gz on this node. For example:

    1
    ./patch_3_1_5_1.sh -d <location of the tar file>
    

The procedure above should be executed on all TDP nodes.

Registering and Installing the Target Patch on the Ambari-Server Node.

The next step is to register and install the target patch. The steps are as follows:

  1. Log in to the Ambari-Server UI.

  2. Perform “Run Service Check” for all the services in the cluster. If any issues are found, resolve them and proceed. “Run Service Check” is available on the dropdown menu of “ACTIONS” in the right top of respective services.

  3. Navigate to the Cluster Admin > Stack and Versions.

  4. Click the Versions tab. You see the version currently running, marked as Current.

  5. Click "Manage Versions".

  6. Proceed to registering a new version by clicking on "Register Version".

  7. Register the patch release as a target version, using the Add Version option under the HDP-3.1 dropdown menu.

  8. Upload Version Definition File patch_3_1_5_1.vdf then click on Read Version Info.

  9. Check "Use local repository" and put the Base URL as file:///var/repo/patch in all three fields Click Save.

  10. Click the Dashboard.

  11. Browse to the Cluster Admin > Stack and Versions.

  12. Click the Versions tab.

  13. You will see the Patch Version 3.1.5.1-316 with a bug icon to indicate that the patch includes a bug fix.

  14. Click INSTALL PACKAGES and click OK to confirm. The Install version operation starts.

This installs the target version on all hosts in the cluster. You can monitor the progress of the install by clicking the “Installing link”. When the installation completes, the "Upgrade" button will replace the "Install Packages" button.

Performing the Patch Upgrade

At this point, you are ready to perform the upgrade, so follow all of the steps below on Ambari-Server node:

  1. Log in to the Ambari-Server UI.

  2. Before starting the upgrade you have to disable the Auto Start Settings in the Cluser: Admin > Service Auto Start.

  3. Browse to the Cluster Admin > Stack and Versions.

  4. Click the Versions tab. The registered and installed target Patch Version 3.1.5.1-316 displays an “Upgrade” button.

  5. Click “Upgrade” on the target version. Based on your current HDP version and the target HDP version, Ambari performs a set of prerequisite checks to determine if you can perform a rolling or an express upgrade. Note that if any required checks pop up, you will need to perform the recommended actions until all checks pass. A dialog displays the options available.

  6. Select the “Express Upgrade” or “Rolling Upgrade” method.

  7. Click “Proceed”.

  8. There may be some manual steps needed at this point. Please follow the instructions given and check the box that says “I have performed the manual steps above” before proceeding.

  9. When the upgrade stages complete, Click “Finalize” to complete the upgrade process.

Updating OS motd (optional)

Once the patching finishes successfully, it is recommended to update the login information in all nodes to ensure that you are running the correct version.

  1. SSH to the TDP node and log in as root.

    You will be welcomed with the following message:

    Thales DDC-TDP 3.1.5.57
    
  2. Run the following command to update it.

    1
    sed -i 's/3.1.5.57/3.1.5.1.57/g' /etc/motd
    

The next time you login to this note you will be welcomed with the following message:

Thales DDC-TDP 3.1.5.1.57