hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-435) Make it easier to access cluster topology information in an AM
Date Mon, 26 Aug 2013 23:47:51 GMT

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

Thomas Weise commented on YARN-435:

For DataTorrent, we require the node report to implement locality constraints for streaming.
We need the initial list (currently only available through ClientRMProtocol), and then use
incremental updates from AMResponse.

> 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: Omkar Vinit Joshi
> 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