• The installed JDK must be a supported version as documented in Java Requirements.
• The same version of the Oracle JDK must be installed on each cluster host.
• The JDK must be installed at /usr/java/jdk-version.

  Important:

• The RHEL-compatible and Ubuntu operating systems supported by Cloudera Enterprise 6 all use AES-256 encryption by default for tickets. To support AES-256 bit encryption, you must install the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy File on all cluster and Hadoop user machines. Cloudera Manager can automatically install the policy files, or you can install them manually. For JCE Policy File installation instructions, see the README.txt file included in the jce_policy-x.zip file.
• On SLES platforms, do not install or try to use the IBM Java version bundled with the SLES distribution. CDH does not run correctly with that version.

  Note: Cloudera, Inc. acquired Oracle JDK software under the Oracle Binary Code License Agreement. Pursuant to Item D(v)(a) of the SUPPLEMENTAL LICENSE TERMS of the Oracle Binary Code License Agreement, use of JDK software is governed by the terms of the Oracle Binary Code License Agreement. By installing the JDK software, you agree to be bound by these terms. If you do not wish to be bound by these terms, then do not install the Oracle JDK.

After completing Step 1: Configure a Repository for Cloudera Manager, you can install the Oracle JDK on the Cloudera Manager Server host using yum as follows:

sudo yum install oracle-j2sdk1.8

You can use Cloudera Manager to install the JDK on the remaining cluster hosts in an upcoming step. Continue to Step 3: Install Cloudera Manager Server.

The Oracle JDK installer is available both as an RPM-based installer for RPM-based systems, and as a .tar.gz file. These instructions are for the .tar.gz file.

1. Download the .tar.gz file for one of the 64-bit supported versions of the Oracle JDK from Java SE 8 Downloads or Java SE 7 Downloads. (These links are correct at the time of writing but change frequently.)
2. Extract the JDK to /usr/java/jdk-version; for example: /usr/java/jdk.1.8.0_<update_version>, where <update_version> is a supported version.
3. Repeat this procedure on all cluster hosts. After you have finished, continue to Step 3: Install Cloudera Manager Server.
4. Set JAVA_HOME to the directory where the JDK is installed. Add the following line to the specified files:

   export JAVA_HOME=/usr/java/jdk.1.8.0_<update_version>

   • Cloudera Manager Server host: /etc/default/cloudera-scm-server. This affects only the Cloudera Manager Server process, and does not affect the Cloudera Management Service roles or CDH service roles. Cloudera Manager handles setting the JAVA_HOME environment variable for managed services.
   • All hosts in an unmanaged deployment: /etc/default/bigtop-utils. You do not need to do this for clusters managed by Cloudera Manager.
5. Follow the instructions in Configuring a Custom Java Home Location. This change affects all CDH processes and Cloudera Management Service roles in the cluster.

  Note: This method of changing the JDK for Cloudera Manager, Cloudera Management Service roles, and CDH processes does not affect the JDK used by other non-Cloudera processes.