Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 17 Dec 2014 18:47:13 +0000 (UTC)
From: "Varun Saxena (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12762053.1418753191000.47512.1418842033971@Atlassian.JIRA>
In-Reply-To: <JIRA.12762053.1418753191000@Atlassian.JIRA>
References: <JIRA.12762053.1418753191000@Atlassian.JIRA>
 <JIRA.12762053.1418753191562@arcas>
Subject: [jira] [Updated] (YARN-2970) NodeLabel operations in RMAdmin CLI
 get missing in help command.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Varun Saxena updated YARN-2970:
-------------------------------
    Attachment: YARN-2970.patch

> NodeLabel operations in RMAdmin CLI get missing in help command.
> ----------------------------------------------------------------
>
>                 Key: YARN-2970
>                 URL: https://issues.apache.org/jira/browse/YARN-2970
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, client, resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Junping Du
>            Assignee: Varun Saxena
>            Priority: Minor
>         Attachments: YARN-2970.patch
>
>
> NodeLabel operations in RMAdmin CLI get missing in help command when I am debugging YARN-313, we should add them on as other cmds:
> {noformat} 
> yarn rmadmin [-refreshQueues] [-refreshNodes] [-refreshResources] [-refreshSuperUserGroupsConfiguration] [-refreshUserToGroupsMappings] [-refreshAdminAcls] [-refreshServiceAcl] [-getGroup [username]] [-updateNodeResource [NodeID] [MemSize] [vCores] ([OvercommitTimeout]) [-help [cmd]]
>    -refreshQueues: Reload the queues' acls, states and scheduler specific properties.
>                 ResourceManager will reload the mapred-queues configuration file.
>    -refreshNodes: Refresh the hosts information at the ResourceManager.
>    -refreshResources: Refresh resources of NodeManagers at the ResourceManager.
>    -refreshSuperUserGroupsConfiguration: Refresh superuser proxy groups mappings
>    -refreshUserToGroupsMappings: Refresh user-to-groups mappings
>    -refreshAdminAcls: Refresh acls for administration of ResourceManager
>    -refreshServiceAcl: Reload the service-level authorization policy file.
>                 ResoureceManager will reload the authorization policy file.
>    -getGroups [username]: Get the groups which given user belongs to.
>    -updateNodeResource [NodeID] [MemSize] [vCores] ([OvercommitTimeout]): Update resource on specific node.
>    -help [cmd]: Displays help for the given command or all commands if none is specified.
>    -addToClusterNodeLabels [label1,label2,label3] (label splitted by ","): add to cluster node labels
>    -removeFromClusterNodeLabels [label1,label2,label3] (label splitted by ","): remove from cluster node labels
>    -replaceLabelsOnNode [node1:port,label1,label2 node2:port,label1,label2]: replace labels on nodes
>    -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 configured yarn.node-labels.fs-store.root-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.
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)