Chris Riccomini created SAMZA-443:
-------------------------------------
Summary: JAVA_HOME is empty even if exported
Key: SAMZA-443
URL: https://issues.apache.org/jira/browse/SAMZA-443
Project: Samza
Issue Type: Bug
Components: container
Affects Versions: 0.8.0
Reporter: Chris Riccomini
Fix For: 0.8.0
We allow developers to customize their JAVA_HOME setting for both the container
and AM. This change was made in SAMZA-308. Recently, we began noticing that if
task.java.home is not set, JAVA_HOME is set to an empty string when
run-container.sh/run-am.sh are executed (both in ProcessJob and YarnJob). This
holds true even if JAVA_HOME has been exported (and is not empty) in the
environment from which the container/am is being started.
This is problematic in the case of YARN, for example, where the NM will
automatically forward its JAVA_HOME setting to containers if JAVA_HOME is not
set. When Samza sets JAVA_HOME to empty, YARN's NM will no longer forward the
JAVA_HOME value.
I believe that we need to fix both ShellCommandBuilder and YarnJob to only set
JAVA_HOME if task.java.home/yarn.am.java.home are not None.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
