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 

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 

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

Reply via email to