[
https://issues.apache.org/jira/browse/TEZ-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649798#comment-14649798
]
Hitesh Shah edited comment on TEZ-2679 at 7/31/15 8:35 PM:
-----------------------------------------------------------
TEZ_AM_LAUNCH_CLUSTER_DEFAULT_CMD_OPTS and
TEZ_TASK_LAUNCH_CLUSTER_DEFAULT_CMD_OPTS are meant to be admin-specified. The
docs could probably use some clarification. Admin-specified env support does
need to be added though.
was (Author: hitesh):
TEZ_AM_LAUNCH_CLUSTER_DEFAULT_CMD_OPTS and
TEZ_TASK_LAUNCH_CLUSTER_DEFAULT_CMD_OPTS are meant to be admin-specified. The
docs could probably use some clarification.
> Admin forms of launch env and java opts settings
> ------------------------------------------------
>
> Key: TEZ-2679
> URL: https://issues.apache.org/jira/browse/TEZ-2679
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Jason Lowe
>
> Tez should provide corresponding admin configs for launch env and java opt
> settings that can be specified in tez-site.xml by cluster admins. For
> example, if users override the launch env settings to setup LD_LIBRARY_PATH
> to just reference their libs then we can fail to load the native Hadoop libs.
> This is currently mitigated by having Tez rely on the MapReduce admin
> properties in many cases, but Tez should provide its own admin settings to
> match the Tez-specific non-admin settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
