[
https://issues.apache.org/jira/browse/TEZ-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044890#comment-14044890
]
Hitesh Shah edited comment on TEZ-1127 at 6/26/14 5:21 PM:
-----------------------------------------------------------
[~bikassaha] Auto-correcting Xmx for tasks based on actual container size will
work. However, it need not hold true for the AM as there is no logic available
to the client as it is not informed about an available container to launch an
AM on. The AM java opts will be decided based on the container ask and not the
actual container size.
was (Author: hitesh):
[~bikassaha] Auto-correcting Xmx for tasks based on actual container size will
work. However, it need not hold true for the AM as there is no logic available
to the client as it is informed about an available container to launch an AM
on. The AM java opts will be decided based on the container ask and not the
actual container size.
> 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
>
>
> 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)
