[
https://issues.apache.org/jira/browse/YARN-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669745#comment-13669745
]
Omkar Vinit Joshi commented on YARN-552:
----------------------------------------
This is related to YARN-435 .. There are certain things which client and AM
both want. It would be useful if we go ahead and expose the common interfaces
in both protocols thereby we don't need to worry about tokens too.
[see
comment|https://issues.apache.org/jira/browse/YARN-435?focusedCommentId=13669570&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13669570]
> Expose resource metrics as part of YarnClusterMetrics
> -----------------------------------------------------
>
> Key: YARN-552
> URL: https://issues.apache.org/jira/browse/YARN-552
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.0.3-alpha
> Reporter: Harsh J
> Assignee: Omkar Vinit Joshi
> Priority: Minor
>
> Right now, the YarnClusterMetrics just has the total number of node managers
> returned in it (when queried from a Client -> RM).
> It would be useful to also expose NodeManager resource capacities and
> scheduler max/min resource limits over it to allow clients to pre-determine
> or pre-compute runtime feasibility without having to request an Application
> first to get some of this information.
> This does not need to be an incompatible change, and we can continue exposing
> the same values as part of the GetNewApplicationResponse too.
--
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
