6. Upgrade Knox

There is service disruption when upgrading Knox. Upgrading Knox requires bringing Knox down completely, upgrading, and starting up again.

For each Knox server, stop the server, switch to the new version, and start the server:
su -l knox "/usr/hdp/2.2.0.0-2041/knox/bin/gateway.sh stop"
hdp-select set knox-server 2.2.4.2-2
su -l knox "/usr/hdp/2.2.4.2-2/knox/bin/gateway.sh start"
Validate the installation:
1. Check /var/log/knox/gateway.log for errors or successful start.
2. Validate cluster access through a WebHDFS API such as LISTSTATUS:
  curl -ivk -u {user}:{password}
  https://{knox-host}:8443/gateway/webhdfs/v1/tmp?op=LISTSTATUS
3. If the Knox admin service is deployed to the gateway instance, the version API should indicate the new version of the Knox code:
  curl -ivk -u {adminuser}:{adminpassword}
  https://{knox-host}:8443/gateway/admin/v1/version

If the upgrade process fails, follow the steps in Downgrading the Cluster, starting with "Downgrade Knox." Otherwise, continue with the next upgrade step.

Legal notices