hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2395) Fair Scheduler : implement fair share preemption at parent queue based on fairSharePreemptionTimeout
Date Thu, 21 Aug 2014 20:33:12 GMT

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

Karthik Kambatla commented on YARN-2395:
----------------------------------------

bq. I removed the old "defaultFairSharePreemptionTimeout" and added a new one "rootFairSharePreemptionTimeout"
This would be backwards incompatible. I propose we leave it as is, but add more documentation
to help understand - If a preemption-timeout is not specified, the queues would inherit their
parent's timeout, and the root queue uses the defaultFairSharePreemptionTimeout. 

> Fair Scheduler : implement fair share preemption at parent queue based on fairSharePreemptionTimeout
> ----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-2395
>                 URL: https://issues.apache.org/jira/browse/YARN-2395
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: fairscheduler
>            Reporter: Ashwin Shankar
>            Assignee: Wei Yan
>         Attachments: YARN-2395-1.patch
>
>
> Currently in fair scheduler, the preemption logic considers fair share starvation only
at leaf queue level. This jira is created to implement it at the parent queue as well.
> It involves :
> 1. Making "check for fair share starvation" and "amount of resource to preempt"  recursive
such that they traverse the queue hierarchy from root to leaf.
> 2. Currently fairSharePreemptionTimeout is a global config. We could make it configurable
on a per queue basis,so that we can specify different timeouts for parent queues.



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

Mime
View raw message