Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 75B02200B61 for ; Mon, 25 Jul 2016 18:12:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 72989160A67; Mon, 25 Jul 2016 16:12:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id C19EF160A7D for ; Mon, 25 Jul 2016 18:12:21 +0200 (CEST) Received: (qmail 23524 invoked by uid 500); 25 Jul 2016 16:12:21 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 23412 invoked by uid 99); 25 Jul 2016 16:12:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2016 16:12:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 904582C0D65 for ; Mon, 25 Jul 2016 16:12:20 +0000 (UTC) Date: Mon, 25 Jul 2016 16:12:20 +0000 (UTC) From: "Eric Payne (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4945) [Umbrella] Capacity Scheduler Preemption Within a queue MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 25 Jul 2016 16:12:22 -0000 [ https://issues.apache.org/jira/browse/YARN-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392184#comment-15392184 ] Eric Payne commented on YARN-4945: ---------------------------------- Thanks [~sunilg]. I appreciate very much any design help and POC help that you can provide. {quote} queue preemption may need to consider multiple factors such - Priority - Fairness - User limit {quote} In general, I would like to separate out the sub-feature pieces of in-queue preemption as much as possible. I am a fan of making small, simple improvements in increments. I believe this makes it easier to understand, test, and review. bq. For initial POC, I was planning priority as I have done an independent POC for priority preemption alone. One thing I don't understand is the use case for a priority policy that is separate from a user limit policy. For my users' use case, the most important of these is user limit. However, I think that in-queue preemption based on user limit needs to be very dependent on app priority and vice-versa. Can you please elaborate? > [Umbrella] Capacity Scheduler Preemption Within a queue > ------------------------------------------------------- > > Key: YARN-4945 > URL: https://issues.apache.org/jira/browse/YARN-4945 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Wangda Tan > > This is umbrella ticket to track efforts of preemption within a queue to support features like: > YARN-2009. YARN-2113. YARN-4781. -- 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