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 D957317E99 for ; Mon, 23 Feb 2015 23:29:16 +0000 (UTC) Received: (qmail 47791 invoked by uid 500); 23 Feb 2015 23:29:13 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 47735 invoked by uid 500); 23 Feb 2015 23:29:13 -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 47723 invoked by uid 99); 23 Feb 2015 23:29:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Feb 2015 23:29:13 +0000 Date: Mon, 23 Feb 2015 23:29:13 +0000 (UTC) From: "Jian He (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-2986) (Umbrella) Support hierarchical and unified scheduler configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334079#comment-14334079 ] Jian He commented on YARN-2986: ------------------------------- Regarding the "policy-properties" take , I have one doubt that what if user specify a policy-property outside of the "policy-properties" tag and non-policy-property inside "policy-properties", will we throw exception or ignore the settings? Ignoring seems confusing to users, as user may have no idea which properties are set correctly and which properties are not. Either way forces users to learn precisely which properties should be inside the policy-properties tags and which ones should not. Each time a new property is added, users also need to be learned. That's non-trivial effort to users. > (Umbrella) Support hierarchical and unified scheduler configuration > ------------------------------------------------------------------- > > Key: YARN-2986 > URL: https://issues.apache.org/jira/browse/YARN-2986 > Project: Hadoop YARN > Issue Type: Improvement > Reporter: Vinod Kumar Vavilapalli > Assignee: Wangda Tan > Attachments: YARN-2986.1.patch > > > Today's scheduler configuration is fragmented and non-intuitive, and needs to be improved. Details in comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)