[
https://issues.apache.org/jira/browse/YARN-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192098#comment-14192098
]
Wangda Tan commented on YARN-2786:
----------------------------------
And I propose to have usage:
{code}
usage: yarn node-labels
-d,--directlyAccessNodeLabelStore Directly access node label store,
with this option, all node label
related operations will NOT connect
RM. Instead, they will access/modify
stored node labels directly. By
default, it is false (access via RM).
AND PLEASE NOTE: if you
configuredyarn.node-labels.fs-store.r
oot-dir to a local directory (instead
of NFS or HDFS), this option will
only work when the command run on the
machine where RM is running.
-h,--help Displays help for all commands.
-l,--listLabels List cluster node-label collection
-m,--listMappings List node-to-label mappings of the
cluster, by default it will return
all node-to-labels mappings of the
cluster.
-n,--nodeId <arg> Works with -listMappings, followed by
nodeId (host:port) or node (host) it
will return node to label mappings
when this specified. Without this
option, all node to labels mappings
will be returned
{code}
Sounds good? :)
> 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
>
> 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)
