Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 28 Oct 2016 18:48:58 +0000 (UTC)
From: "Sunil G (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12711498.1398875224000.120264.1477680538662@Atlassian.JIRA>
In-Reply-To: <JIRA.12711498.1398875224000@Atlassian.JIRA>
References: <JIRA.12711498.1398875224000@Atlassian.JIRA> <JIRA.12711498.1398875224477@arcas>
Subject: [jira] [Updated] (YARN-2009) Intra-queue preemption for app
 priority support ProportionalCapacityPreemptionPolicy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 28 Oct 2016 18:49:00 -0000


     [ https://issues.apache.org/jira/browse/YARN-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sunil G updated YARN-2009:
--------------------------
    Attachment: YARN-2009.0016.patch

Thank you very much [~curino] for the comments.

bq.question: in TestProportionalCapacityPreemptionPolicyIntraQueue.testSimpleIntraQueuePreemption() why is app4 seeing
app3 and app4 are of same priority. However app3 is added first to queue, and then app4. Hence according to FIFO within same priority level, app4 is last submitted. Hence app4 will be selected to preempt first.

bq.is maxIntraQueuePreemptableLimit set to 50% a reasonable default? it seems maybe high?
yes. Decreased to 20% now.

Thank [~eepayne]. Agreeing that this  patch is majorly concentrating in solving single user's priority inversion problem

> Intra-queue preemption for app priority support ProportionalCapacityPreemptionPolicy
> ------------------------------------------------------------------------------------
>
>                 Key: YARN-2009
>                 URL: https://issues.apache.org/jira/browse/YARN-2009
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Devaraj K
>            Assignee: Sunil G
>              Labels: oct16-medium
>         Attachments: YARN-2009.0001.patch, YARN-2009.0002.patch, YARN-2009.0003.patch, YARN-2009.0004.patch, YARN-2009.0005.patch, YARN-2009.0006.patch, YARN-2009.0007.patch, YARN-2009.0008.patch, YARN-2009.0009.patch, YARN-2009.0010.patch, YARN-2009.0011.patch, YARN-2009.0012.patch, YARN-2009.0013.patch, YARN-2009.0014.patch, YARN-2009.0015.patch, YARN-2009.0016.patch
>
>
> While preempting containers based on the queue ideal assignment, we may need to consider preempting the low priority application containers first.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org