hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4083) Add a discovery mechanism for the scheduler addresss
Date Thu, 27 Aug 2015 06:18:46 GMT

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

Jian He commented on YARN-4083:
-------------------------------

One other thing to think about is what if NM died, should AM fall back to the RM?
Also, in case of RM HA, there will be multiple RM scheduler addresses, simply swapping out
a single scheduler address will not work.

> Add a discovery mechanism for the scheduler addresss
> ----------------------------------------------------
>
>                 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)

Mime
View raw message