[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350464#comment-14350464
 ] 

Hudson commented on YARN-2786:
--

FAILURE: Integrated in Hadoop-Mapreduce-trunk #2074 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2074/])
YARN-2786. Created a yarn cluster CLI and seeded with one command for listing 
node-labels collection. Contributed by Wangda Tan. (vinodkv: rev 
138c9cadee32da4d17be9835461bde646825d8d5)
* hadoop-yarn-project/CHANGES.txt
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestClusterCLI.java
* hadoop-yarn-project/hadoop-yarn/bin/yarn
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ClusterCLI.java
* hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd


> 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
> Fix For: 2.7.0
>
> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.patch, YARN-2786-20150304-2-branch2.patch, 
> YARN-2786-20150304-2-trunk-to-kick-jenkins.patch, 
> YARN-2786-20150304-2-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350426#comment-14350426
 ] 

Hudson commented on YARN-2786:
--

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #124 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/124/])
YARN-2786. Created a yarn cluster CLI and seeded with one command for listing 
node-labels collection. Contributed by Wangda Tan. (vinodkv: rev 
138c9cadee32da4d17be9835461bde646825d8d5)
* hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestClusterCLI.java
* hadoop-yarn-project/hadoop-yarn/bin/yarn
* hadoop-yarn-project/CHANGES.txt
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ClusterCLI.java


> 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
> Fix For: 2.7.0
>
> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.patch, YARN-2786-20150304-2-branch2.patch, 
> YARN-2786-20150304-2-trunk-to-kick-jenkins.patch, 
> YARN-2786-20150304-2-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350407#comment-14350407
 ] 

Hudson commented on YARN-2786:
--

FAILURE: Integrated in Hadoop-Hdfs-trunk-Java8 #115 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Java8/115/])
YARN-2786. Created a yarn cluster CLI and seeded with one command for listing 
node-labels collection. Contributed by Wangda Tan. (vinodkv: rev 
138c9cadee32da4d17be9835461bde646825d8d5)
* hadoop-yarn-project/hadoop-yarn/bin/yarn
* hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd
* hadoop-yarn-project/CHANGES.txt
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestClusterCLI.java
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ClusterCLI.java


> 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
> Fix For: 2.7.0
>
> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.patch, YARN-2786-20150304-2-branch2.patch, 
> YARN-2786-20150304-2-trunk-to-kick-jenkins.patch, 
> YARN-2786-20150304-2-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350411#comment-14350411
 ] 

Hudson commented on YARN-2786:
--

FAILURE: Integrated in Hadoop-Hdfs-trunk #2056 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2056/])
YARN-2786. Created a yarn cluster CLI and seeded with one command for listing 
node-labels collection. Contributed by Wangda Tan. (vinodkv: rev 
138c9cadee32da4d17be9835461bde646825d8d5)
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestClusterCLI.java
* hadoop-yarn-project/hadoop-yarn/bin/yarn
* hadoop-yarn-project/CHANGES.txt
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ClusterCLI.java
* hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd


> 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
> Fix For: 2.7.0
>
> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.patch, YARN-2786-20150304-2-branch2.patch, 
> YARN-2786-20150304-2-trunk-to-kick-jenkins.patch, 
> YARN-2786-20150304-2-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350304#comment-14350304
 ] 

Hudson commented on YARN-2786:
--

FAILURE: Integrated in Hadoop-Yarn-trunk #858 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/858/])
YARN-2786. Created a yarn cluster CLI and seeded with one command for listing 
node-labels collection. Contributed by Wangda Tan. (vinodkv: rev 
138c9cadee32da4d17be9835461bde646825d8d5)
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestClusterCLI.java
* hadoop-yarn-project/CHANGES.txt
* hadoop-yarn-project/hadoop-yarn/bin/yarn
* hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ClusterCLI.java


> 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
> Fix For: 2.7.0
>
> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.patch, YARN-2786-20150304-2-branch2.patch, 
> YARN-2786-20150304-2-trunk-to-kick-jenkins.patch, 
> YARN-2786-20150304-2-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350297#comment-14350297
 ] 

Hudson commented on YARN-2786:
--

FAILURE: Integrated in Hadoop-Yarn-trunk-Java8 #124 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk-Java8/124/])
YARN-2786. Created a yarn cluster CLI and seeded with one command for listing 
node-labels collection. Contributed by Wangda Tan. (vinodkv: rev 
138c9cadee32da4d17be9835461bde646825d8d5)
* hadoop-yarn-project/CHANGES.txt
* hadoop-yarn-project/hadoop-yarn/bin/yarn
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestClusterCLI.java
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ClusterCLI.java
* hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd


> 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
> Fix For: 2.7.0
>
> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.patch, YARN-2786-20150304-2-branch2.patch, 
> YARN-2786-20150304-2-trunk-to-kick-jenkins.patch, 
> YARN-2786-20150304-2-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349286#comment-14349286
 ] 

Hudson commented on YARN-2786:
--

FAILURE: Integrated in Hadoop-trunk-Commit #7269 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/7269/])
YARN-2786. Created a yarn cluster CLI and seeded with one command for listing 
node-labels collection. Contributed by Wangda Tan. (vinodkv: rev 
138c9cadee32da4d17be9835461bde646825d8d5)
* hadoop-yarn-project/CHANGES.txt
* hadoop-yarn-project/hadoop-yarn/bin/yarn
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/cli/ClusterCLI.java
* hadoop-yarn-project/hadoop-yarn/bin/yarn.cmd
* 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/cli/TestClusterCLI.java


> 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
> Fix For: 2.7.0
>
> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.patch, YARN-2786-20150304-2-branch2.patch, 
> YARN-2786-20150304-2-trunk-to-kick-jenkins.patch, 
> YARN-2786-20150304-2-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347955#comment-14347955
 ] 

Hadoop QA commented on YARN-2786:
-

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12702659/YARN-2786-20150304-2-trunk-to-kick-jenkins.patch
  against trunk revision 722b479.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/6854//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6854//console

This message is automatically generated.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.patch, YARN-2786-20150304-2-branch2.patch, 
> YARN-2786-20150304-2-trunk-to-kick-jenkins.patch, 
> YARN-2786-20150304-2-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347799#comment-14347799
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12702629/YARN-2786-20150304-2-branch2.patch
  against trunk revision 722b479.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6852//console

This message is automatically generated.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.patch, YARN-2786-20150304-2-branch2.patch, 
> YARN-2786-20150304-2-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347728#comment-14347728
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12702629/YARN-2786-20150304-2-branch2.patch
  against trunk revision c66c3ac.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6851//console

This message is automatically generated.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.patch, YARN-2786-20150304-2-branch2.patch, 
> YARN-2786-20150304-2-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347672#comment-14347672
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12702617/YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch
  against trunk revision ed70fa1.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:red}-1 findbugs{color}.  The patch appears to introduce 1 new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/6848//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/6848//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6848//console

This message is automatically generated.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk-to-rekick-Jenkins.patch, 
> YARN-2786-20150304-1-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347598#comment-14347598
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12702610/YARN-2786-20150304-1-branch2.patch
  against trunk revision ed70fa1.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6847//console

This message is automatically generated.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.patch, YARN-2786-20150304-1-branch2.patch, 
> YARN-2786-20150304-1-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Vinod Kumar Vavilapalli (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347481#comment-14347481
 ] 

Vinod Kumar Vavilapalli commented on YARN-2786:
---

Actually, this won't apply to branch-2. Can you upload the branch-2 patch too? 
Tx.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Vinod Kumar Vavilapalli (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347464#comment-14347464
 ] 

Vinod Kumar Vavilapalli commented on YARN-2786:
---

Looks good. Checking this in.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346150#comment-14346150
 ] 

Hadoop QA commented on YARN-2786:
-

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12702312/YARN-2786-20150303-1-trunk.patch
  against trunk revision 5af693f.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/6830//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6830//console

This message is automatically generated.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-without-yarn.cmd.patch, 
> YARN-2786-20150303-1-trunk.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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269905#comment-14269905
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12690906/YARN-2786-20150108-1-without-yarn.cmd.patch
  against trunk revision 708b1aa.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client:

  org.apache.hadoop.yarn.client.api.impl.TestAMRMClient

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/6282//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6282//console

This message is automatically generated.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269878#comment-14269878
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12690906/YARN-2786-20150108-1-without-yarn.cmd.patch
  against trunk revision 20625c8.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/6281//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6281//console

This message is automatically generated.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-without-yarn.cmd.patch, 
> YARN-2786-20150108-1-full.patch, YARN-2786-20150108-1-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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Allen Wittenauer (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268672#comment-14268672
 ] 

Allen Wittenauer commented on YARN-2786:


'cluster' does not come alphabetically after 'node'.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268647#comment-14268647
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12690672/YARN-2786-20150107-1-without-yarn.cmd.patch
  against trunk revision ef237bd.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:red}-1 findbugs{color}.  The patch appears to introduce 1 new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client:

  org.apache.hadoop.yarn.client.TestResourceTrackerOnHA
  
org.apache.hadoop.yarn.client.TestApplicationClientProtocolOnHA

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/6275//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-YARN-Build/6275//artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-client.html
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6275//console

This message is automatically generated.

> 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, 
> YARN-2786-20150107-1-full.patch, YARN-2786-20150107-1-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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Vinod Kumar Vavilapalli (JIRA)]

[ 
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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Allen Wittenauer (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219598#comment-14219598
 ] 

Allen Wittenauer commented on YARN-2786:


bq. Does this make sense?

No, it doesn't. It completely ignores 20+ years of industry experience towards 
operations and configuration management of large scale installations.  This is 
mostly exemplified by this comment:

bq.  I'd rather have the tools call an API instead of 'automatically' sshing 
into 1000 machines and changing labels.

I'm completely stunned and saddened by this ignorance.  I suspect that there is 
a corporate mandate to get Ambari working as a third tier scheduling system by 
dictating where services run.  But that mandate (and its likely required 
deliverable time) has put blinders on the architecture and may very well cause 
long term pain and could potentially prevent other, more complex needs from 
being met.  

The only silver linings I'm seeing are thus:
* We still have time to undo the damage either now or in 3.x.
* Selfishly, this will give me years of material about how not to design a 
system to be operationally friendly.

> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Wangda Tan (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208519#comment-14208519
 ] 

Wangda Tan commented on YARN-2786:
--

bq.  Essentially: adding this feature creates the invalid label problem you are 
hoping to avoid!
As what Vinod commented above, CLI/REST API to add labels not means it is used 
by human and typing it character-by-character on keyboard. And also, the 
distributed script is also created by human, they're identically same regarding 
to invalid labels could be added.

Distributed configuration by automatically executing script has its benefit of 
course, but many things will be hard to interpret without human's intervene. 
E.g. if an admin know some nodes in the cluster will be removed soon, and add a 
label "temporary" to these node. It will need more effort to do the same thing 
via script. Many attributes like "temporary" are subjective, I think we should 
have both of them exists. 

Does this make sense?

> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Vinod Kumar Vavilapalli (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208498#comment-14208498
 ] 

Vinod Kumar Vavilapalli commented on YARN-2786:
---

bq.   If the operations teams are the ones setting up the cluster, shouldn't 
they know what labels they want to use? 
No, it is not just a human operator. The reason why we have REST API, CLIs etc 
is for tools to be able to automatically do this. I thought that was reasonably 
obvious. A human operator may not care about this, but that doesn't mean we 
should not add these for automation tools. I'd rather have the tools call an 
API instead of 'automatically' sshing into 1000 machines and changing labels.

bq. Now instead of being able to control the labels either via code or 
configuration management, we're going to trust humans to type things in at the 
command line. Essentially: adding this feature creates the invalid label 
problem you are hoping to avoid! 
Same as above. It's not humans. And like I said, operators interacting with the 
system via configuration files can do so via the distributed-configuration 
mechanism.

bq. You seem to be confusing 'random' and 'ephemeral'. 
Not quite. An admin decides to remove a label from all nodes in the cluster. 
Except he/she cannot reach the node. The distributed configuration makes the 
cluster behave in very not-funny ways. This is my example of 
random-unwarranted-label.

bq. So in summary, again, I'm completely and totally against the ability to add 
labels from the command line. It's a big flaw in an implementation full of 
flaws.
In summary again, you are against it for manual administration and that's fine 
- you are still getting the distributed configuration. You can't say no to APIs 
that you don't use - others will use it.

> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Allen Wittenauer (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208300#comment-14208300
 ] 

Allen Wittenauer commented on YARN-2786:


bq. By the time I started on HOD, those experiments were presumably over, so I 
never heard about them.

I'm not surprised... otherwise you'd realize what a mess having a state file 
for this info causes. Every single time a node gets added, every single time a 
node gets modified, every single time a node gets deleted, this state file is 
going to have to verified.  This is in addition to the already existing 
includex2, excludex2, and slaves files.

bq.Further, you don't want a central list of valid labels which I disagree 
with. 

The part that no one has had a reasonable explanation for is where exactly 
these invalid labels are coming from.  If the operations teams are the ones 
setting up the cluster, shouldn't they know what labels they want to use?  The 
only conclusion I can come up with is Ambari or Cloudera Manager.  So, yes, I 
can see why people would need protection against them.

bq. Others like me can turn it on to avoid 
random-labels-bubbling-up-in-my-cluster madness.

You seem to be confusing 'random' and 'ephemeral'.  

The whole reason I'm against adding this change is that it just makes the state 
file situation that much worse.  Now instead of being able to control the 
labels either via code or configuration management, we're going to trust humans 
to type things in at the command line. Essentially: adding this feature 
*creates* the invalid label problem you are hoping to avoid!  

So in summary, again, I'm completely and totally against the ability to add 
labels from the command line.  It's a big flaw in an implementation full of 
flaws.

> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Vinod Kumar Vavilapalli (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203210#comment-14203210
 ] 

Vinod Kumar Vavilapalli commented on YARN-2786:
---

bq. c) I realize neither of you were there when we ran HOD and dealt with 
Torque where a normal course of action was to just delete the configuration and 
start it over because the label configuration was completely unmanageable. I 
also recognize that my -1 on this "feature" is falling on deaf ears and you're 
going to get this in come hell or high water. 
By the time I started on HOD, those experiments were presumably over, so I 
never heard about them.

IAC, the crux of what you want is a per node script based configuration. That 
IS happening as we speak as part of the tickets I referred to. Further, you 
don't want a central list of valid labels which I disagree with. But sure, we 
will make this configurable to or not to require a central list so that you can 
turn it off. Others like me can turn it on to avoid 
random-labels-bubbling-up-in-my-cluster madness.

> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Allen Wittenauer (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202883#comment-14202883
 ] 

Allen Wittenauer commented on YARN-2786:


a) cluster should be sorted in the usage output and in the case statement.  

b) dnl doesn't mean "directly-access-node-label-store" to me due to the 
dropping of letters

c) I realize neither of you were there when we ran HOD and dealt with Torque 
where a normal course of action was to just delete the configuration and start 
it over because the label configuration was completely unmanageable. I also 
recognize that my -1 on this "feature" is falling on deaf ears and you're going 
to get this in come hell or high water.  

> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Vinod Kumar Vavilapalli (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201392#comment-14201392
 ] 

Vinod Kumar Vavilapalli commented on YARN-2786:
---

[~aw], any comments after my update above : 
https://issues.apache.org/jira/browse/YARN-2786?focusedCommentId=14196953&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14196953
 ?

Will go ahead with this if I don't hear in a couple of days. Thanks.

> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197151#comment-14197151
 ] 

Hadoop QA commented on YARN-2786:
-

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12679359/YARN-2786-20141104-2-without-yarn.cmd.patch
  against trunk revision 2e1d9a4.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5727//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5727//console

This message is automatically generated.

> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197064#comment-14197064
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12679295/YARN-2786-20141104-1-without-yarn.cmd.patch
  against trunk revision 1eed102.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 
13 warning messages.
See 
https://builds.apache.org/job/PreCommit-YARN-Build/5724//artifact/patchprocess/diffJavadocWarnings.txt
 for details.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The following test timeouts occurred in 
hadoop-hdfs-project/hadoop-hdfs:

org.apache.hadoop.hdfs.TestEncryptionZones

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5724//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5724//console

This message is automatically generated.

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Vinod Kumar Vavilapalli (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196953#comment-14196953
 ] 

Vinod Kumar Vavilapalli commented on YARN-2786:
---

I see the discussion on YARN-796, YARN-2495.

Both the implementations are going to be done soon, so we can agree to disagree 
on having both a decentralized way and a central way to assign labels against 
nodes.

bq. "Where did this label come from? I guess someone manually added it via the 
shell at some point?"
This is simply audit/lineage. As part of YARN-2495, we can make sure an admin 
can only configure it using only one of the mechanisms and not both. I doubt if 
this is necessary, but sure.

bq. This is actually supporting my claim that adding cluster for this purpose 
is a bad idea, 
Don't follow. We need a "yarn cluster" for ton of other things that we don't 
have today.

I can already list a few
{code}
yarn cluster --list-nodes
yarn cluster --list-nodes --status=UNHEALTHY
yarn cluster --list-racks
yarn cluster --current-resource-usage
{code}

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Allen Wittenauer (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196923#comment-14196923
 ] 

Allen Wittenauer commented on YARN-2786:


bq.  I believe this has been discussed to death at YARN-796 & friends. We now 
are doing YARN-2495 too. Sites who prefer to choose one over the other can do 
so without any concern.

Could you point specifically to where this specific feature was discussed?  

I've very much against doing this feature. This feels a lot like the mess that 
is /proc on Linux:  a writable interface with an indeterminate state on 
restart.  I'll just come out and say it: it's a terrible idea that makes 
systems much harder to support over the long haul.  ("Where did this label come 
from?  I guess someone manually added it via the shell at some point?"  or "I 
want to start all of my labels over.  Oh, I have to run a bunch of commands to 
do it instead of editing a file?")

bq.  I quickly read through the entire JIRA - "yarn cluster" is way better than 
the original "yarn node-labels". Specifically, given we also have "yarn node" 
returning labels, it should address your concerns?

This is actually supporting my claim that adding cluster for this purpose is a 
bad idea, given that the weirdo node command also returns labels in an 
unprivileged manner. :)

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Vinod Kumar Vavilapalli (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196889#comment-14196889
 ] 

Vinod Kumar Vavilapalli commented on YARN-2786:
---

I quickly read through the entire JIRA - "yarn cluster" is way better than the 
original "yarn node-labels". Specifically, given we also have "yarn node" 
returning labels, it should address your concerns?

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Vinod Kumar Vavilapalli (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196874#comment-14196874
 ] 

Vinod Kumar Vavilapalli commented on YARN-2786:
---

bq. What is the difference between a user running a command that adds an hbase 
attribute to a node, the configuration file listing the hbase attribute to a 
node, the configuration on the node manager that says it has the hbase 
attribute, and the dynamic script telling the NM has the hbase attribute?
I believe this has been discussed to death at YARN-796 & friends. We now are 
doing YARN-2495 too. Sites who prefer to choose one over the other can do so 
without any concern.

bq. This is exactly why I wanted an analog of dfsadmin -report. This is a user 
consistency issue. The rmadmin -report should list all the nodes as well as 
what their node labels are (amongst other interesting things).
Agree this is a user consistency issue. But "dfsadmin -report" is not great at 
all, no matter how much you got used to it. It's not an admin privilege to list 
the nodes - any user who has the right ACLs should be able to do it. We don't 
need to keep compatibility with HDFS.

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Allen Wittenauer (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196853#comment-14196853
 ] 

Allen Wittenauer commented on YARN-2786:


bq. like a node doesn't know "I should run hbase, I should run storm, etc.". 
Basically script method can only get basic attribute of the node.


What is the difference between a user running a command that adds an hbase 
attribute to a node, the configuration file listing the hbase attribute to a 
node, the configuration on the node manager that says it has the hbase 
attribute, and the dynamic script telling the NM has the hbase attribute?

The biggest problem I see with having a more public API way of adding 
attributes is that this means we need to keep state and all the management of 
that state... even between restarts.  This just isn't viable long term without 
a lot of heavy lifting.

bq. yarn cluster

This is *exactly* why I wanted an analog of dfsadmin -report.  This is a user 
consistency issue.  The rmadmin -report should list all the nodes as well as 
what their node labels are (amongst other interesting things).

So, no on yarn cluster as well.  

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196615#comment-14196615
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12679277/YARN-2786-20141104-1-full.patch
  against trunk revision 1eed102.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5722//console

This message is automatically generated.

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Vinod Kumar Vavilapalli (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196540#comment-14196540
 ] 

Vinod Kumar Vavilapalli commented on YARN-2786:
---

Quick comments on the patch
 - Let's mark the new CLI class as Private
 - Let's use _hyphenated-options_ instead of _CamelCaseOptions_

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195406#comment-14195406
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12679065/YARN-2786-20141103-1-without-yarn.cmd.patch
  against trunk revision 35d353e.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The following test timeouts occurred in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client:

org.apache.hadoop.yarn.client.TestResourceTrackerOnHA

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5710//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5710//console

This message is automatically generated.

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195326#comment-14195326
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12679064/YARN-2786-20141103-1-full.patch
  against trunk revision 35d353e.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5709//console

This message is automatically generated.

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Wangda Tan (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195204#comment-14195204
 ] 

Wangda Tan commented on YARN-2786:
--

[~cwelch],
Thanks for comments,
bq. bin/yarn drop s
Addressed

bq. listLables should be listNodeLabels ...
Addressed

bq. Can't we use the visible for test annotation?
Addressed

bq. test is still using the node-labels command instead of cluster ...
Oh, my bad, I forgot to change that, the field will not be ignored in Java 
side, so the both of test case or actual using "yarn cluster ..." will be 
succeeded.

Will upload a patch soon.

Thanks,
Wangda


> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Craig Welch (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195131#comment-14195131
 ] 

Craig Welch commented on YARN-2786:
---

The "node" command isn't a good fit for this aspect of node-labels, as it is 
not an operation or query on nodes as such, but on the set of node labels 
recognized by the cluster.  If we don't want to tie it to the resource manager 
(not sure we can't, but it sounds as though we want to keep it distinct) then 
we need something new.  I actually preferred the original "node-labels" 
command, but "cluster" is ok if we believe that other things will come along in 
the future which fit this definition (and I could see that happen).

Code items:

bin/yarn
prints cluster informations - information is singular and plural, you can drop 
the s

ClusterCLI.java
listLables should be listNodeLabels (we've gone to that everywhere b/c there 
will likely be other kinds of labels, we should stay consistent, especially as 
"cluster" cmd name has lost any notion of "nodelabelness")

//Make it protected to make unit test can change it
Can't we use the visible for test annotation?

It looks like the test is still using the node-labels command instead of 
cluster, did something go wrong with the patch (maybe forgot to restage)?  Can 
you make sure the unit test + patch code are consistent and the tests pass?




> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194190#comment-14194190
 ] 

Hadoop QA commented on YARN-2786:
-

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12678852/YARN-2786-20141102-3.patch
  against trunk revision 27715ec.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-YARN-Build/5693//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5693//console

This message is automatically generated.

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Wangda Tan (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194173#comment-14194173
 ] 

Wangda Tan commented on YARN-2786:
--

Offline discussed with [~cnauroth], it is a known issue when yarn.cmd (windows 
file) and other linux file mixed together in a patch. So what we can do is 
either manually modify the file ending of the patch, makes it mixed with \r\n 
and \n. Or we can commit two patches separately.

I will first upload a patch without yarn.cmd changes, kick Jenkins to get early 
report.

> 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
>
>
> 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)

[jira] [Commented] (YARN-2786) Create yarn cluster CLI to enable list node labels collection

[Hadoop QA (JIRA)]

[ 
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194143#comment-14194143
 ] 

Hadoop QA commented on YARN-2786:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12678843/YARN-2786-20141102-2.patch
  against trunk revision 27715ec.

{color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5691//console

This message is automatically generated.

> 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
>
>
> 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)