Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F1DE217E18 for ; Tue, 16 Jun 2015 03:57:00 +0000 (UTC) Received: (qmail 11835 invoked by uid 500); 16 Jun 2015 03:57:00 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 11763 invoked by uid 500); 16 Jun 2015 03:57:00 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 11748 invoked by uid 99); 16 Jun 2015 03:57:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jun 2015 03:57:00 +0000 Date: Tue, 16 Jun 2015 03:57:00 +0000 (UTC) From: "Wei Shao (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-3806) Proposal of Generic Scheduling Framework for YARN MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Wei Shao created YARN-3806: ------------------------------ Summary: Proposal of Generic Scheduling Framework for YARN Key: YARN-3806 URL: https://issues.apache.org/jira/browse/YARN-3806 Project: Hadoop YARN Issue Type: Improvement Components: scheduler Reporter: Wei Shao Currently, A typical YARN cluster runs many different kinds of applications= : production applications, ad hoc user applications, long running services = and so on. Different YARN scheduling policies may be suitable for different= applications. For example, capacity scheduling can manage production appli= cations well since application can get guaranteed resource share, fair sche= duling can manage ad hoc user applications well since it can enforce fairne= ss among users. However, current YARN scheduling framework doesn=E2=80=99t = have a mechanism for multiple scheduling policies work hierarchically in on= e cluster. YARN-3306 talked about many issues of today=E2=80=99s YARN scheduling frame= work, and proposed a per-queue policy driven framework. In detail, it suppo= rted different scheduling policies for leaf queues. However, support of dif= ferent scheduling policies for upper level queues is not seriously consider= ed yet.=20 A generic scheduling framework is proposed here to address these limitation= s. It supports different policies for any queue consistently. The proposal = tries to solve many other issues in current YARN scheduling framework as we= ll. -- This message was sent by Atlassian JIRA (v6.3.4#6332)