[
https://issues.apache.org/jira/browse/TEZ-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044894#comment-14044894
]
Rohini Palaniswamy commented on TEZ-1127:
-----------------------------------------
Yes. Having -Xmx set based on container size setting is a good thing to have.
Many people misconfigure that. But we also have a lot of specialized cases
where people custom tune their jvm. For eg: when there is lot of native memory
usage they set lower -Xmx than usual to avoid container getting killed because
it exceeds physical memory limits. So I hope there is a way to turn off that
auto tuning setting. I have seen other things like GC settings tuning, -D
options, etc apart from Xmx.
> 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)
