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

Reply via email to