hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandy Ryza (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-596) Use scheduling policies throughout the queue hierarchy to decide which containers to preempt
Date Thu, 29 May 2014 04:06:02 GMT

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

Sandy Ryza commented on YARN-596:
---------------------------------

I just committed this to trunk and branch-2.  Thanks Wei for the patch and Ashwin for taking
a look.

> Use scheduling policies throughout the queue hierarchy to decide which containers to
preempt
> --------------------------------------------------------------------------------------------
>
>                 Key: YARN-596
>                 URL: https://issues.apache.org/jira/browse/YARN-596
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.0.3-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>             Fix For: 2.5.0
>
>         Attachments: YARN-596.patch, YARN-596.patch, YARN-596.patch, YARN-596.patch,
YARN-596.patch, YARN-596.patch, YARN-596.patch, YARN-596.patch, YARN-596.patch, YARN-596.patch,
YARN-596.patch, YARN-596.patch
>
>
> In the fair scheduler, containers are chosen for preemption in the following way:
> All containers for all apps that are in queues that are over their fair share are put
in a list.
> The list is sorted in order of the priority that the container was requested in.
> This means that an application can shield itself from preemption by requesting it's containers
at higher priorities, which doesn't really make sense.
> Also, an application that is not over its fair share, but that is in a queue that is
over it's fair share is just as likely to have containers preempted as an application that
is over its fair share.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message