From yarn-issues-return-29035-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Mon Jun 9 10:09:03 2014 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 34EB011209 for ; Mon, 9 Jun 2014 10:09:03 +0000 (UTC) Received: (qmail 43639 invoked by uid 500); 9 Jun 2014 10:09:02 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 43590 invoked by uid 500); 9 Jun 2014 10:09:02 -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 43533 invoked by uid 99); 9 Jun 2014 10:09:02 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jun 2014 10:09:02 +0000 Date: Mon, 9 Jun 2014 10:09:02 +0000 (UTC) From: "Andrey Stepachev (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-2134) FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings 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-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Stepachev updated YARN-2134: ----------------------------------- Description: AllocationConfiguration doesn't fully qualify queue names with respect to 'root.' prefix. Such behaviour leads to situation where settings for nested queue doesn't take effect. Consider following config (working example in broken-hier-queues.diff attached) sub queue settings were not applied by method queueConf.getMaxResources. {code:xml} 2048mb,10vcores 512mb,1vcores {code} I made patch, which unifies QueueName operations (remove those indexOf copy pastes) and apply some of settings in hierarchical manner (say preemption timeout can be used from parent queue instead of global default). Also it is interesting to introduce type safe object QueueName and replace String in interfaces, and I have made an attempt (https://github.com/octo47/hadoop-common/tree/feature/octo/fs-queue-name), but looks like it lead to some inconsitancy and I think that it is not necessary right now). was: AllocationConfiguration doesn't fully qualify queue names with respect to 'root.' prefix. Such behaviour leads to situation where settings for nested queue doesn't take effect. Consider following config (working example in broken-hier-queues.diff attached) sub queue settings were not applied by method queueConf.getMaxResources. {code:xml} 2048mb,10vcores 512mb,1vcores {code} I made patch, which unifies QueueName operations (remove those indexOf copy pastes) and apply some of settings in hierarchical manner (say preemption timeout can be used from parent queue instead of global default). Also it is interesting to introduce type safe object QueueName and replace String in interfaces, and I have made an attempt (https://github.com/octo47/hadoop-common/tree/feature/octo/fs-queue-name), but looks like it lead to some inconstancy and I think that it is not necessary right now). > FairSchduler AllocationConfiguration doesn't treat hierarchical queues settings > ------------------------------------------------------------------------------- > > Key: YARN-2134 > URL: https://issues.apache.org/jira/browse/YARN-2134 > Project: Hadoop YARN > Issue Type: Bug > Components: fairscheduler > Affects Versions: 2.5.0 > Reporter: Andrey Stepachev > Attachments: YARN-2134.diff, broken-hier-queues.diff > > > AllocationConfiguration doesn't fully qualify queue names with respect to 'root.' prefix. Such behaviour leads to situation where settings for nested queue doesn't take effect. > Consider following config (working example in broken-hier-queues.diff attached) sub queue settings were not applied by method queueConf.getMaxResources. > {code:xml} > > 2048mb,10vcores > > 512mb,1vcores > > > {code} > I made patch, which unifies QueueName operations (remove those indexOf copy pastes) and apply some of settings in hierarchical manner (say preemption timeout can be used from parent queue instead of global default). > Also it is interesting to introduce type safe object QueueName and replace String in interfaces, and I have made an attempt (https://github.com/octo47/hadoop-common/tree/feature/octo/fs-queue-name), but looks like it lead to some inconsitancy and I think that it is not necessary right now). -- This message was sent by Atlassian JIRA (v6.2#6252)