Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 24 Jun 2014 21:44:29 +0000 (UTC)
From: "Mayank Bansal (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12714823.1400262569361.40787.1403646269240@arcas>
In-Reply-To: <JIRA.12714823.1400262569361@arcas>
References: <JIRA.12714823.1400262569361@arcas>
Subject: [jira] [Updated] (YARN-2069) Add cross-user preemption within
 CapacityScheduler's leaf-queue
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mayank Bansal updated YARN-2069:
--------------------------------

    Attachment: YARN-2069-trunk-2.patch

Thanks for the review.

I don't have any easy way now to seprate the YARN-2022 and this patch as I am changing the same code and run it through junkins.
I will rebase this patch once YARN-2022 is committed.

Thanks,
Mayank

> Add cross-user preemption within CapacityScheduler's leaf-queue
> ---------------------------------------------------------------
>
>                 Key: YARN-2069
>                 URL: https://issues.apache.org/jira/browse/YARN-2069
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Mayank Bansal
>         Attachments: YARN-2069-trunk-1.patch, YARN-2069-trunk-2.patch
>
>
> Preemption today only works across queues and moves around resources across queues per demand and usage. We should also have user-level preemption within a queue, to balance capacity across users in a predictable manner.


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