Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-443

JAVA_HOME is empty even if exported

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 0.8.0
    • Component/s: container
    • Labels:
      None

      Description

      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.

        Attachments

        1. SAMZA-443.patch
          3 kB
          Yan Fang

          Activity

            People

            • Assignee:
              closeuris Yan Fang
              Reporter:
              criccomini Chris Riccomini
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: