You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2014/07/25 00:45:39 UTC

[jira] [Updated] (TEZ-1127) Add TEZ_TASK_JAVA_OPTS and TEZ_ENV configs to specify values from config

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

Bikas Saha updated TEZ-1127:
----------------------------

    Attachment: TEZ-1127.addendum.patch

Addendum that changes the java.opts to launch.cmd-opts and makes things consistent.

> Add TEZ_TASK_JAVA_OPTS and TEZ_ENV configs to specify values from config
> ------------------------------------------------------------------------
>
>                 Key: TEZ-1127
>                 URL: https://issues.apache.org/jira/browse/TEZ-1127
>             Project: Apache Tez
>          Issue Type: Sub-task
>    Affects Versions: 0.4.0
>            Reporter: Pala M Muthaia
>            Assignee: Bikas Saha
>             Fix For: 0.5.0
>
>         Attachments: PIG-TEZ-1127.patch, TEZ-1127.1.patch, TEZ-1127.2.patch, TEZ-1127.addendum.patch
>
>
> There is no global setting available to specify JVM parameters for tez tasks (e.g: specifying native library location with java.library.path). Yarn allows specifying application.classpath, but not java opts. The only option right now is to set mapreduce.map.java.opts in the tez job config (or hive.tez.java.opts for Hive on Tez).
> Suggestion from Bikas, while discussing this in tez-user group, is tez should have "TEZ_TASK_JAVA_OPTS so that you don’t have to specify this via mapreduce configuration parameters"



--
This message was sent by Atlassian JIRA
(v6.2#6252)