Chapter 10. Change the JDK Version
During your initial Ambari Server Setup, you selected the JDK to use or provided a path to a custom JDK already installed on your hosts. After setting up your cluster, you may change the JDK version using the following procedure.
The choice of JDK is dependent on which HDP Stack you plan to install in your cluster. The following table indicates which JDKs work with which Stacks.
Stack
JDKs
HDP 2.3
JDK 1.7 or JDK 1.8
HDP 2.0, 2.1 or 2.2
JDK 1.7
[Important] Important
If you plan to upgrade between Stacks (for example, go from HDP 2.2 -> HDP 2.3) do not change the JDK until you have successfully upgraded the Stack and are running the cluster on the target Stack. For example, the high-level process should follow:
Running HDP 2.2 with JDK 1.7.
Perform Stack upgrade to HDP 2.3.
Change JDK from 1.7 to 1.8 (using the following procedure).
How to change the JDK version for an existing cluster
Re-run Ambari Server Setup.
ambari-server setup
At the prompt to change the JDK, Enter y.
Do you want to change Oracle JDK [y/n] (n)? y
At the prompt to choose a JDK, Enter 1 to change the JDK to v1.8.
[1] - Oracle JDK 1.8
[2] - Oracle JDK 1.7
[3] - Custom JDK
If you choose Oracle JDK 1.8 or Oracle JDK 1.7, the JDK you choose downloads and installs automatically on the Ambari Server host. This option requires that you have an internet connection. You must install this JDK on all hosts in the cluster to this same path.
If you choose Custom JDK, verify or add the custom JDK path on all hosts in the cluster. Use this option if you want to use OpenJDK or do not have an internet connection (and have pre-installed the JDK on all hosts).
After setup completes, you must restart each component for the new JDK to be used by the Hadoop services.
Using the Ambari Web UI, do the following tasks:
Restart each component
Restart each host
Restart all services