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 83C0017511 for ; Sat, 25 Oct 2014 07:04:39 +0000 (UTC) Received: (qmail 44927 invoked by uid 500); 25 Oct 2014 07:04:34 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 44882 invoked by uid 500); 25 Oct 2014 07:04:34 -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 44847 invoked by uid 99); 25 Oct 2014 07:04:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Oct 2014 07:04:34 +0000 Date: Sat, 25 Oct 2014 07:04:34 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-2744) Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist 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-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wangda Tan updated YARN-2744: ----------------------------- Issue Type: Sub-task (was: Bug) Parent: YARN-2492 > Under some scenario, it is possible to end up with capacity scheduler configuration that uses labels that no longer exist > ------------------------------------------------------------------------------------------------------------------------- > > Key: YARN-2744 > URL: https://issues.apache.org/jira/browse/YARN-2744 > Project: Hadoop YARN > Issue Type: Sub-task > Components: capacityscheduler > Affects Versions: 2.5.1 > Reporter: Sumit Mohanty > Assignee: Wangda Tan > Priority: Critical > Fix For: 2.6.0 > > > Use the following steps: > * Ensure default in-memory storage is configured for labels > * Define some labels and assign nodes to labels (e.g. define two labels and assign both labels to the host on a one host cluster) > * Invoke refreshQueues > * Modify capacity scheduler to create two top level queues and allow access to the labels from both the queues > * Assign appropriate "label + queue" specific capacities > * Restart resource manager > Noticed that RM starts without any issues. The labels are not preserved across restart and thus the capacity-scheduler ends up using labels that are no longer present. > At this point submitting an application to YARN will not succeed as there are no resources available with the labels. -- This message was sent by Atlassian JIRA (v6.3.4#6332)