[
https://issues.apache.org/jira/browse/YARN-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628247#comment-13628247
]
Alejandro Abdelnur commented on YARN-45:
----------------------------------------
Nice, the proposed functionality comes quite handy for some stuff I'm working
on.
Regarding the question on how to model the PreemptRequest, have you thought
about the following alternative?
* The PreemptRequest would contain only a Set<PreemptResource>.
* PreemptResource has the following properties: a String location, a Resource
capability
* The PreemptResource location can be ANY, a rack or a node.
* The PreemptResource capability is the total capacity that should be released.
* The AM, if taking the hint, would release containers that match the location
and add up to the PreemptResource capability.
By doing this, you give full control to the AM to decide what to release by
grouping any containers that match the location.
Thoughts?
> Scheduler feedback to AM to release containers
> ----------------------------------------------
>
> Key: YARN-45
> URL: https://issues.apache.org/jira/browse/YARN-45
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: resourcemanager
> Reporter: Chris Douglas
> Assignee: Carlo Curino
> Attachments: YARN-45.patch
>
>
> The ResourceManager strikes a balance between cluster utilization and strict
> enforcement of resource invariants in the cluster. Individual allocations of
> containers must be reclaimed- or reserved- to restore the global invariants
> when cluster load shifts. In some cases, the ApplicationMaster can respond to
> fluctuations in resource availability without losing the work already
> completed by that task (MAPREDUCE-4584). Supplying it with this information
> would be helpful for overall cluster utilization [1]. To this end, we want to
> establish a protocol for the RM to ask the AM to release containers.
> [1] http://research.yahoo.com/files/yl-2012-003.pdf
--
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
