hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-435) Make it easier to access cluster topology information in an AM
Date Fri, 26 Apr 2013 00:52:16 GMT

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

Vinod Kumar Vavilapalli commented on YARN-435:

I think that opening a new connection isn't really a problem. I propose:
 - Keeping the protocols separate - ClientRMProtocol and AMRMProtocol and not duplicate any
 - Expect AMs to open two connections always. The AMRMClient library can do this for java
 - For secure mode, make the ClientRMProtocol also accept AMTokens. Once we do that, any AM
even in secure mode can talk to RM on both the protocols. After this and YARN-613, AMToken
becomes a single sign-on token - with a AMToken, an AM can talk to ClientRMProtocol and AMRMProtocol
on ResourceManager and also on ContainerManagerProtocol on NodeManager. 
> Make it easier to access cluster topology information in an AM
> --------------------------------------------------------------
>                 Key: YARN-435
>                 URL: https://issues.apache.org/jira/browse/YARN-435
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
> ClientRMProtocol exposes a getClusterNodes api that provides a report on all nodes in
the cluster including their rack information. 
> However, this requires the AM to open and establish a separate connection to the RM in
addition to one for the AMRMProtocol. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message