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 ED111189FC for ; Wed, 27 May 2015 22:37:17 +0000 (UTC) Received: (qmail 98765 invoked by uid 500); 27 May 2015 22:37:17 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 98712 invoked by uid 500); 27 May 2015 22:37:17 -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 98700 invoked by uid 99); 27 May 2015 22:37:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 May 2015 22:37:17 +0000 Date: Wed, 27 May 2015 22:37:17 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-3581) Deprecate -directlyAccessNodeLabelStore in RMAdminCLI 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-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14561874#comment-14561874 ] Wangda Tan commented on YARN-3581: ---------------------------------- Think about this, this is not a critical issue for 2.7.1, so I think it's better not to commit to 2.7.1. Removed it from target version. Committing. > Deprecate -directlyAccessNodeLabelStore in RMAdminCLI > ----------------------------------------------------- > > Key: YARN-3581 > URL: https://issues.apache.org/jira/browse/YARN-3581 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api, client, resourcemanager > Reporter: Wangda Tan > Assignee: Naganarasimha G R > Attachments: YARN-3581.20150525-1.patch, YARN-3581.20150528-1.patch > > > In 2.6.0, we added an option called "-directlyAccessNodeLabelStore" to make RM can start with label-configured queue settings. After YARN-2918, we don't need this option any more, admin can configure queue setting, start RM and configure node label via RMAdminCLI without any error. > In addition, this option is very restrictive, first it needs to run on the same node where RM is running if admin configured to store labels in local disk. > Second, when admin run the option when RM is running, multiple process write to a same file can happen, this could make node label store becomes invalid. -- This message was sent by Atlassian JIRA (v6.3.4#6332)