Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 24 Feb 2016 12:30:18 +0000 (UTC)
From: "Ashwin Shankar (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12910603.1446694161000.132684.1456317018490@Atlassian.JIRA>
In-Reply-To: <JIRA.12910603.1446694161000@Atlassian.JIRA>
References: <JIRA.12910603.1446694161000@Atlassian.JIRA>
 <JIRA.12910603.1446694161856@arcas>
Subject: [jira] [Commented] (YARN-4333) Fair scheduler should support
 preemption within queue
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ashwin Shankar commented on YARN-4333:
--------------------------------------

I'm out of town until end of this week. Will take a look when I get back. Thanks!

> Fair scheduler should support preemption within queue
> -----------------------------------------------------
>
>                 Key: YARN-4333
>                 URL: https://issues.apache.org/jira/browse/YARN-4333
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler
>    Affects Versions: 2.6.0
>            Reporter: Tao Jie
>            Assignee: Tao Jie
>         Attachments: YARN-4333.001.patch, YARN-4333.002.patch, YARN-4333.003.patch
>
>
> Now each app in fair scheduler is allocated its fairshare, however  fairshare resource is not ensured even if fairSharePreemption is enabled.
> Consider: 
> 1, When the cluster is idle, we submit app1 to queueA,which takes maxResource of queueA.  
> 2, Then the cluster becomes busy, but app1 does not release any resource, queueA resource usage is over its fairshare
> 3, Then we submit app2(maybe with higher priority) to queueA. Now app2 has its own fairshare, but could not obtain any resource, since queueA is still over its fairshare and resource will not assign to queueA anymore. Also, preemption is not triggered in this case.
> So we should allow preemption within queue, when app is starved for fairshare.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)