[
https://issues.apache.org/jira/browse/TEZ-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044896#comment-14044896
]
Hitesh Shah commented on TEZ-1127:
----------------------------------
[~rohini] I guess the question is if you set the AM container size to 2.5 G or
4 G, are you ok with Tez setting the java opts by calculating Xmx to be 80% of
container size?
What we are trying to do is make it easy for users to do configuration. i.e.
they set the container size and Xmx/Xms is automatically calculated. If a user
wants to add additional opts like GC flags, etc, they can still do so but those
should be static configs that should not need to be changed if the container
size is changed.
> 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)
