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 4EE1918268 for ; Wed, 17 Jun 2015 16:41:04 +0000 (UTC) Received: (qmail 50137 invoked by uid 500); 17 Jun 2015 16:41:04 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 50095 invoked by uid 500); 17 Jun 2015 16:41:04 -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 50083 invoked by uid 99); 17 Jun 2015 16:41:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2015 16:41:03 +0000 Date: Wed, 17 Jun 2015 16:41:03 +0000 (UTC) From: "Wei Shao (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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 [ https://issues.apache.org/jira/browse/YARN-3806?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14590= 061#comment-14590061 ]=20 Wei Shao commented on YARN-3806: -------------------------------- The original motivation for this proposal is, in Rocket Fuel, we want to de= velop and evaluate two new scheduling policies YARN-3807 & YARN-3808. Howev= er, current yarn doesn't support per queue policy, and YARN-3306 which is w= orking in progress may not match all requirements of these new policies. Fo= r example, YARN-3808 requires that the queue can create sub queue for users= & applications dynamically with specific configurations, YARN-3807 require= s that the queue can scale up/down dynamically and applications can have ow= n configurations. > 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 > Attachments: ProposalOfGenericSchedulingFrameworkForYARN-V1.0.pdf= , ProposalOfGenericSchedulingFrameworkForYARN-V1.1.pdf > > > Currently, a typical YARN cluster runs many different kinds of applicatio= ns: production applications, ad hoc user applications, long running service= s and so on. Different YARN scheduling policies may be suitable for differe= nt applications. For example, capacity scheduling can manage production app= lications well since application can get guaranteed resource share, fair sc= heduling can manage ad hoc user applications well since it can enforce fair= ness among users. However, current YARN scheduling framework doesn=E2=80=99= t have a mechanism for multiple scheduling policies work hierarchically in = one cluster. > YARN-3306 talked about many issues of today=E2=80=99s YARN scheduling fra= mework, and proposed a per-queue policy driven framework. In detail, it sup= ported different scheduling policies for leaf queues. However, support of d= ifferent scheduling policies for upper level queues is not seriously consid= ered yet.=20 > A generic scheduling framework is proposed here to address these limitati= ons. It supports different policies for any queue consistently. The proposa= l tries to solve many other issues in current YARN scheduling framework as = well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)