hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2786) Create yarn node-labels CLI to enable list node labels collection and node labels mapping
Date Fri, 31 Oct 2014 20:25:34 GMT

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

Wangda Tan commented on YARN-2786:

bq. 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 overhead.
As always emphasized, script method cannot resolve all problems, 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.

"yarn node" is the CLI for getting status for RMNode, but here
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. 
2) 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.
I think I've described the reason here. And also, I don't think put a "yarn node" or "yarn
node-labels" is a *internal* of Hadoop. If no such "yarn queue" / "yarn node", user should
use command like, "yarn -listNodeStatus", etc. -- That is just an apple to another apple to

> 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

View raw message