hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-801) Expose container locations and capabilities in the RM REST APIs
Date Thu, 13 Jun 2013 15:27:20 GMT

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

Alejandro Abdelnur commented on YARN-801:

Traversing the scheduler data structures & preparing all this info in large cluster under
load it can be expensive and if we do a lock to do this data collection/generation we'll be
adding contention to the scheduler. I think we should model this as a service independent
of the scheduler which receives async events on container allocations/terminations and keeps
its own data structure. This would decouple any contention from the scheduler from calls to
this REST API.

> Expose container locations and capabilities in the RM REST APIs
> ---------------------------------------------------------------
>                 Key: YARN-801
>                 URL: https://issues.apache.org/jira/browse/YARN-801
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: api, resourcemanager
>    Affects Versions: 2.0.4-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
> It would be useful to be able to query container allocation info via the RM REST APIs.
 We should be able to query per application, and for each container we should provide (at
> * location
> * resource capabilty

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