You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Yan Fang (JIRA)" <ji...@apache.org> on 2014/09/17 00:03:35 UTC

[jira] [Assigned] (SAMZA-308) Allow the container JVM to be customized

     [ https://issues.apache.org/jira/browse/SAMZA-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yan Fang reassigned SAMZA-308:
------------------------------

    Assignee: Yan Fang

> Allow the container JVM to be customized
> ----------------------------------------
>
>                 Key: SAMZA-308
>                 URL: https://issues.apache.org/jira/browse/SAMZA-308
>             Project: Samza
>          Issue Type: New Feature
>          Components: yarn
>    Affects Versions: 0.7.0
>            Reporter: Martin Kleppmann
>            Assignee: Yan Fang
>              Labels: newbie
>
> When running a container, the JAVA_HOME environment variable is currently inherited from the parent process (the JobRunner in the case of LocalJobFactory, the NodeManager in the case of YarnJobFactory). It would be nice to allow a job to specify a JAVA_HOME path as part of its configuration, so that a job can choose to run in a particular JVM version (e.g. allowing the YARN cluster and the jobs' JVM versions to be updated independently from each other).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)