Upgrade the Knox Gateway
If you are not currently using Ambari to manage your Hadoop cluster, you need to upgrade Knox manually to the latest version. Because “rolling upgrades” are now supported in HDP 2.5.5, it is not important which version of Knox you are currently running, only that you have an instance of the Knox Gateway running.
Note | |
---|---|
If you have not already installed Knox, refer to the "Install the Knox RPMs on the Knox Server" section of the Non-Ambari Cluster Installation Guide for instructions on how to install and configure the Knox Gateway. |
Before upgrading the Knox Gateway, there are a several steps you must follow to ensure your configuration files, settings, and topology files can be copied to the new Knox Gateway instance when the upgrade is complete, which are described below.
Back up your existing
conf
directory if you have not already done so.Stop each Knox server if you have not already done so.
su -l knox /usr/hdp/{the current Knox version}/knox/bin/gateway.sh stop
Select the HDP server version you are upgrading to after you have stopped each Knox server if you have not already done so.
hdp-select set knox-server {the HDP server version}
Note The
su
commands in this section use "knox" to represent the Knox Service user. If you are using another name for your Knox Service user, you need to substitute your Knox Service user name for "knox" in each of thesu
commands.For , the default paths for Knox change. Upgrade Knox in order to update these paths.
Restore the backed up security directory. This places the master secret and keystores back in place for the new deployment.
Start the Gateway:
su -knox -c "/usr/hdp/current/knox-server/bin/gateway.sh start"
Unzip your previously saved configuration directory (the
conf
directory you backed up in step 1) into the new /var/log/knox/gateway.conf directory to import these files.Restart the Knox server to complete the upgrade.
su -l knox /usr/hdp/{the new HDP server version}/knox/bin/gateway.sh start