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

Reply via email to