[
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192382#comment-14192382
]
Allen Wittenauer commented on YARN-2786:
----------------------------------------
bq. 1) User can specify a labels for node before NM register to RM, so it is
not a part of RMNode. The user scenario is, admin can specify labels for nodes
before RM is running to pre-setup the cluster.
I can't think of a possible use case for this at all that isn't already covered
by the scripted method. This feels a lot like unnecessary overheard.
bq. We should have an API for user to get all labels in the cluster, it is not
good to put in "yarn node" as well.
Why isn't it good to put in 'yarn node', other than this dumb idea that some
have that the CLI commands should reflect what the code does on the inside?
(Hint: user's don't care or know or understand the internals of Hadoop.)
> Create yarn node-labels CLI to enable list node labels collection and node
> labels mapping
> -----------------------------------------------------------------------------------------
>
> 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
>
>
> 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
> 2) list node-to-label mappings even if the node hasn't registered to RM.
> The command should start with "yarn node-labels ..."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
