hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4610) Reservations continue looking for one app causes other apps to starve
Date Wed, 20 Jan 2016 22:03:39 GMT

     [ 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.002.patch

Nice catch, Tom!  I think we need to preserve the original amount needed to unreserve and
reset back to that before evaluating each application.  That way we'll honor the amount needed
that can be passed in from the parent.  Updated the branch-2.7 patch accordingly.

It's always zero from the parent in trunk so no need to preserve it, but I can update the
trunk patch to match if desired.

> 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-branch-2.7.002.patch, 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)

Mime
View raw message