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 595D4178CA for ; Fri, 21 Nov 2014 00:06:35 +0000 (UTC) Received: (qmail 32366 invoked by uid 500); 21 Nov 2014 00:06:35 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 32321 invoked by uid 500); 21 Nov 2014 00:06:35 -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 32310 invoked by uid 99); 21 Nov 2014 00:06:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Nov 2014 00:06:35 +0000 Date: Fri, 21 Nov 2014 00:06:35 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection 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-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220269#comment-14220269 ] Vinod Kumar Vavilapalli commented on YARN-2786: ----------------------------------------------- Let me conclude this, it has gone on for far too long. We should agree to disagree. It's ops _and_ developers, not _or_. You want to manually configure through scripts, you will get it in the distributed-config setup. The rest of us want to configure programmatically through APIs, we will have that as an option. I don't see a technical argument against what is done so far, only opinions on which is the right approach. This JIRA is not the place for this discussion, if you have more qualms about this, you should comment on YARN-796. Suggestions to change design in a leaf JIRA is not constructive. > Create yarn cluster CLI to enable list node labels collection > ------------------------------------------------------------- > > Key: YARN-2786 > URL: https://issues.apache.org/jira/browse/YARN-2786 > Project: Hadoop YARN > Issue Type: Sub-task > Components: api, client, resourcemanager > Reporter: Wangda Tan > Assignee: Wangda Tan > Attachments: YARN-2786-20141031-1.patch, YARN-2786-20141031-2.patch, YARN-2786-20141102-2.patch, YARN-2786-20141102-3.patch, YARN-2786-20141103-1-full.patch, YARN-2786-20141103-1-without-yarn.cmd.patch, YARN-2786-20141104-1-full.patch, YARN-2786-20141104-1-without-yarn.cmd.patch, YARN-2786-20141104-2-full.patch, YARN-2786-20141104-2-without-yarn.cmd.patch > > > With YARN-2778, we can list node labels on existing RM nodes. But it is not enough, we should be able to: > 1) list node labels collection > The command should start with "yarn cluster ...", in the future, we can add more functionality to the "yarnClusterCLI" -- This message was sent by Atlassian JIRA (v6.3.4#6332)