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 "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2014/04/14 00:38:18 UTC

[jira] [Resolved] (YARN-1722) AMRMProtocol should have a way of getting all the nodes in the cluster

     [ https://issues.apache.org/jira/browse/YARN-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli resolved YARN-1722.
-------------------------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: 2.5.0)

Dup of YARN-435. YARN-435 didn't make progress not because of any technical reasons. We are going to work on it soon. Closing this as dup.

> AMRMProtocol should have a way of getting all the nodes in the cluster
> ----------------------------------------------------------------------
>
>                 Key: YARN-1722
>                 URL: https://issues.apache.org/jira/browse/YARN-1722
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Bikas Saha
>
> There is no way for an AM to find out the names of all the nodes in the cluster via the AMRMProtocol. An AM can only at best ask for containers at * location. The only way to get that information is via the ClientRMProtocol but that is secured by Kerberos or RMDelegationToken while the AM has an AMRMToken. This is a pretty important piece of missing functionality. There are other jiras opened about getting cluster topology etc. but they havent been addressed due to a clear definition of cluster topology perhaps. Adding a means to at least get the node information would be a good first step.



--
This message was sent by Atlassian JIRA
(v6.2#6252)