This is the documentation for Cloudera Enterprise 5.8.x. Documentation for other versions is available at Cloudera Documentation.

Java Development Kit Installation

Some installation paths require that you install the Oracle Java Development Kit on hosts before deploying Cloudera Manager, CDH, and managed services. To install the Oracle JDK, follow the instructions in Installing the Oracle JDK. The completed installation, or any already existing installation, must meet the following requirements.

Requirements

  Important:
  • You cannot upgrade from JDK 1.7 to JDK 1.8 while upgrading to CDH 5.3. The cluster must already be running CDH 5.3 when you upgrade to JDK 1.8.
  • If you are upgrading from a lower major version of the JDK to JDK 1.8 or from JDK 1.6 to JDK 1.7 and you are using AES-256 bit encryption, you must install new encryption policy files. (In a Cloudera Manager deployment, Cloudera Manager offers you an option to automatically install the policy files; for unmanaged deployments, install them manually.) See If you are Using AES-256 Encryption, install the JCE Policy File.

    For both managed and unmanaged deployments, you must also ensure that the Java Truststores are retained during the upgrade. (See Creating Truststores.)

  • On SLES 11 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.

Installing the Oracle JDK

The Oracle JDK installer is available both as an RPM-based installer for RPM-based systems, and as a binary installer for other systems.

  1. Download the .tar.gz file for one of the 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.7.0_nn or /usr/java/jdk.1.8.0_nn, where nn is a supported version.
  3. Set JAVA_HOME to the directory where the JDK is installed, for example 
    export JAVA_HOME=/usr/java/jdk.1.7.0_nn
    in the following files on Cloudera Manager Server and cluster hosts:
    • Cloudera Manager Server - /etc/default/cloudera-scm-server. This change affects only the Cloudera Manager Server process, and does not affect the Cloudera Management Service roles.
    • Cloudera Manager package-based or unmanaged deployment - /etc/default/bigtop-utils
  4. 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.
Page generated July 8, 2016.