[
https://issues.apache.org/jira/browse/YARN-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated YARN-4610:
-----------------------------
Attachment: YARN-4610.branch-2.7.001.patch
Patch for branch-2.7. Clearing of the amount needed to unreserve had to be in
a different place for 2.7 since there were multiple places that could set that
value (i.e.: canAssignToThisQueue also sets it).
> Reservations continue looking for one app causes other apps to starve
> ---------------------------------------------------------------------
>
> Key: YARN-4610
> URL: https://issues.apache.org/jira/browse/YARN-4610
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 2.7.1
> Reporter: Jason Lowe
> Assignee: Jason Lowe
> Priority: Blocker
> Attachments: YARN-4610.001.patch, YARN-4610.branch-2.7.001.patch
>
>
> CapacityScheduler's LeafQueue has "reservations continue looking" logic that
> allows an application to unreserve elsewhere to fulfil a container request on
> a node that has available space. However in 2.7 that logic seems to break
> allocations for subsequent apps in the queue. Once a user hits its user
> limit, subsequent apps in the queue for other users receive containers at a
> significantly reduced rate.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
