Upgrading to Version 3.1.6

This upgrade procedure applies only to the TDP upgrade from version 3.1.5.1 to 3.1.6.

Upgrade Script

1. Download 610-000621-002_SW_TDP_Upgrade_v316_RevA.zip from the customer portal and extract Upgrade_to_3.1.6_tdp_upgrade.sh and rpms_316.tar.gz to the /var/tmp directory on the host node.

2. Navigate to the /var/tmp directory. Give execution permission to the upgrade script and it:

   cd /var/tmp
   chmod +x Upgrade_to_3.1.6_tdp_upgrade.sh
   ./Upgrade_to_3.1.6_tdp_upgrade.sh
   

   Repeat the above steps on all nodes.

3. If the current node has Knox enabled, you have to generate a new certificate with the SAN field (Subject Alternative Name) in it.

   Note

   When the Knox service was first installed by Ambari, a self-signed certificate was created internally. However, starting from CM 2.8, the SAN field is mandatory in the Knox server certificate. As older TDP versions created certificates that did not define it, CM 2.8 will be unable to connect.

   To generate a new certificate with the SAN field:

   1. SSH to the node where the Knox gateway is installed, run the command:

      sed -i '/^openssl req -x509 -sha256 -newkey rsa:2048/,+5 d' /root/setup/update_knox_cert.sh
      

      Tip

      Although the above command is only required on a node that has Knox running on it, it is recommended to run it on other nodes in case you decide to enable Knox on them in the future.

   2. Follow the instructions in Updating and Exporting the Knox Server Certificate to generate a new certificate for this node and configure Knox to use it.

   3. Update the configuration of Data Discovery and Classification with the new certificate. Refer to the Configuring TDP section in the Data Discovery and Classification documentation to learn more.

Registering and Installing the Target Version

1. Log in to Ambari and browse to Cluster Admin > STACK and VERSIONS screen.

2. Click the VERSIONS tab. You can see the version currently running, marked as CURRENT.

   

   Note

   The full version depends on the TDP version that you are currently running.

3. Click MANAGE VERSIONS and click OK to confirm in the Manage Versions pop up box.

   

4. Proceed to registering a new version by clicking REGISTER VERSION.

   

5. Put 6.0-316 to complete the version number in the Name: field so that the full name should be HDP-3.1.6.0-316, like so:

   

6. Select Use local repository and put file:///var/repo/hdp-316 as the Base URL in these fields:

   

   After you click SAVE, you will see in the Admin/Versions screen that the new version has been successfully created and you can now install it.

   

7. Go to the Dashboard > Cluster Admin screen and click the VERSIONS tab.

   

   You can see that a new version - 3.1.6-316 - is now registered and (showing as "INSTALLED").

8. Click to expand the INSTALLED menu in the new registered version, select Install Packages, and then click OK to confirm to start the installation of the new version.

Performing the Upgrade

After you installed the new version you can upgrade your TDP to that version.

1. Before starting the upgrade make sure you have the "Auto Start" setting disabled. You can check this in the Cluster Admin > Service Auto Start screen.

   

   Auto Start will be initially enabled. Slide the toggle switch so that it becomes grey and says Disabled. After you disable "Auto Start" you can perform the upgrade.

2. Browse to Cluster Admin > STACK and VERSIONS screen.

3. Click the VERSIONS tab. The registered and installed target TDP version now features an UPGRADE button.

   

4. Click the UPGRADE button on the target version to start the upgrade.
   Ambari performs a set of checks, depending on your current TDP version and the target TDP version.

   1. Select Express Upgrade or Rolling Upgrade method.

   2. Click PROCEED to continue.

5. When the upgrade stages complete, click FINALIZE to complete the upgrade process.