[
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.1.patch
Patch
1) Adds TezConfiguration for AM/Task launch-cmd-opts, launch-env and log-level
2) Creates common methods for setting these from the configs/defaults. This
fixes a few inconsistencies in existing code
3) Sets up defaults so that they remain the same as existing usage
4) Remove MR dependent code from existing examples
Default env's are added if not already present. Env classpath/ld_lib_path are
appended to existing values since we know that they can be appended.
Existing tests should cover this. Manually verified by changing log level to
info<->debug for AM and Task in a single node cluster and inspecting the log
files.
> 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
> Attachments: TEZ-1127.1.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)
