question JAVA_HOME not set for clients in Archives of Support Questions (Read Only)

JAVA_HOME not set for clients

jeroenr — Fri, 05 May 2017 15:34:33 GMT

CDM version: 5.7.1

I've set the Java Home Directory in the hosts config to /opt/java/jdk

It's picked up properly by all services, but not by clients

For example running the yarn command, it will complain JAVA_HOME is not set

The file used to check for JAVA_HOME is:

/opt/cloudera/parcels/CDH-5.7.1-1.cdh5.7.1.p0.11/lib/bigtop-utils/bigtop-detect-javahome

Apparently this file is not checking the hosts config setting. I'm surprised by that.

The info for this option says:

Explicitly set the value of JAVA_HOME for all processes. This will override the auto-detection logic that is normally used.

Why doesn't it apply to client processes?

thanks

Re: JAVA_HOME not set for clients

gwen — Fri, 12 May 2017 17:34:02 GMT

Perhaps this will help?

https://community.cloudera.com/t5/Cloudera-Manager-Installation/Error-JAVA-HOME-is-not-set-and-Java-could-not-be-found/m-p/18974/highlight/true#M2441

Re: JAVA_HOME not set for clients

jeroenr — Wed, 17 May 2017 09:00:53 GMT

a case was opened with support, confirmed that the Java home directory override currently only applies to servers, not to clients.This can lead to Java version inconsistencies.

This will be resolved in a future version, and can be tracked via OPSAPS-40053

To specify a Java home directory for all clients, set the variable in file /etc/default/bigtop-utils