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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/09/05 02:01:41 UTC

[jira] [Commented] (YARN-4083) Add a discovery mechanism for the scheduler address

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

Allen Wittenauer commented on YARN-4083:
----------------------------------------

How does this work when the container is actually a Linux container and not a fake yarn-level container?

> Add a discovery mechanism for the scheduler address
> ---------------------------------------------------
>
>                 Key: YARN-4083
>                 URL: https://issues.apache.org/jira/browse/YARN-4083
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager, resourcemanager
>            Reporter: Subru Krishnan
>            Assignee: Subru Krishnan
>
> Today many apps like Distributed Shell, REEF, etc rely on the fact that the HADOOP_CONF_DIR of the NM is on the classpath to discover the scheduler address. This JIRA proposes the addition of an explicit discovery mechanism for the scheduler address



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