You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Gera Shegalov (JIRA)" <ji...@apache.org> on 2016/03/11 11:30:06 UTC

[jira] [Commented] (YARN-4789) Provide helpful exception for non-PATH-like conflict with admin.user.env

    [ https://issues.apache.org/jira/browse/YARN-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190773#comment-15190773 ] 

Gera Shegalov commented on YARN-4789:
-------------------------------------

I see the following options to deal with it:
# silently ignore/replace the user-provided value by the one in admin.env
# inform the user that the variable is provided by the cluster admins.

001 patch for the latter

> Provide helpful exception for non-PATH-like conflict with admin.user.env
> ------------------------------------------------------------------------
>
>                 Key: YARN-4789
>                 URL: https://issues.apache.org/jira/browse/YARN-4789
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.2
>            Reporter: Gera Shegalov
>            Assignee: Gera Shegalov
>         Attachments: YARN-4789.001.patch
>
>
> Environment variables specified in mapreduce.admin.user.env are supposed to be paths (class, shell, library) and they can be merged with the user-provided values. However, it's also possible that the cluster admins specify some non-PATH-like variable such as JAVA_HOME. In this case if there is the same variable provided by the user, we'll get a concatenation that does not make sense and is difficult to debug.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)