hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhishek Modi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-9178) TestRMAdminCli#testHelp is failing in trunk
Date Sat, 05 Jan 2019 02:35:00 GMT

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

Abhishek Modi commented on YARN-9178:
-------------------------------------


*Stacktrace*
java.lang.AssertionError: 
Help messages: 
 rmadmin is the command to execute YARN administrative commands.
The full syntax is: 

yarn rmadmin [-refreshQueues] [-refreshNodes [-g|graceful [timeout in seconds] -client|server]]
[-refreshNodesResources] [-refreshSuperUserGroupsConfiguration] [-refreshUserToGroupsMappings]
[-refreshAdminAcls] [-refreshServiceAcl] [-getGroup [username]] [-addToClusterNodeLabels <"label1(exclusive=true),label2(exclusive=false),label3">]
[-removeFromClusterNodeLabels <label1,label2,label3>] [-replaceLabelsOnNode <"node1[:port]=label1,label2
node2[:port]=label1"> [-failOnUnknownNodes]] [-directlyAccessNodeLabelStore] [-refreshClusterMaxPriority]
[-updateNodeResource [NodeID] [MemSize] [vCores] ([OvercommitTimeout]) or -updateNodeResource
[NodeID] [ResourceTypes] ([OvercommitTimeout])] [-help [cmd]]

   -refreshQueues: Reload the queues' acls, states and scheduler specific properties. 
		ResourceManager will reload the mapred-queues configuration file.
   -refreshNodes [-g|graceful [timeout in seconds] -client|server]: Refresh the hosts information
at the ResourceManager. Here [-g|graceful [timeout in seconds] -client|server] is optional,
if we specify the timeout then ResourceManager will wait for timeout before marking the NodeManager
as decommissioned. The -client|server indicates if the timeout tracking should be handled
by the client or the ResourceManager. The client-side tracking is blocking, while the server-side
tracking is not. Omitting the timeout, or a timeout of -1, indicates an infinite timeout.
Known Issue: the server-side tracking will immediately decommission if an RM HA failover occurs.
   -refreshNodesResources: 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. 
		ResourceManager will reload the authorization policy file.
   -getGroups [username]: Get the groups which given user belongs to.
   -addToClusterNodeLabels <"label1(exclusive=true),label2(exclusive=false),label3">:
add to cluster node labels. Default exclusivity is true
   -removeFromClusterNodeLabels <label1,label2,label3> (label splitted by ","): remove
from cluster node labels
   -replaceLabelsOnNode <"node1[:port]=label1,label2 node2[:port]=label1,label2"> [-failOnUnknownNodes]
: replace labels on nodes (please note that we do not support specifying multiple labels on
a single host for now.)
		[-failOnUnknownNodes] is optional, when we set this option, it will fail if specified nodes
are unknown.
   -directlyAccessNodeLabelStore: This is DEPRECATED, will be removed in future releases.
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.
   -refreshClusterMaxPriority: Refresh cluster max priority
   -updateNodeResource [NodeID] [MemSize] [vCores] ([OvercommitTimeout]) 
		or
		[NodeID] [resourcetypes] ([OvercommitTimeout]). : Update resource on specific node.
   -help [cmd]: Displays help for the given command or all commands if none is specified.

Generic options supported are:
-conf <configuration file>        specify an application configuration file
-D <property=value>               define a value for a given property
-fs <file:///|hdfs://namenode:port> specify default filesystem URL to use, overrides
'fs.defaultFS' property from configurations.
-jt <local|resourcemanager:port>  specify a ResourceManager
-files <file1,...>                specify a comma-separated list of files to be copied
to the map reduce cluster
-libjars <jar1,...>               specify a comma-separated list of jar files to be
included in the classpath
-archives <archive1,...>          specify a comma-separated list of archives to be unarchived
on the compute machines

The general command line syntax is:
command [genericOptions] [commandOptions]

rmadmin is the command to execute YARN administrative commands.
The full syntax is: 

yarn rmadmin [-refreshQueues] [-refreshNodes [-g|graceful [timeout in seconds] -client|server]]
[-refreshNodesResources] [-refreshSuperUserGroupsConfiguration] [-refreshUserToGroupsMappings]
[-refreshAdminAcls] [-refreshServiceAcl] [-getGroup [username]] [-addToClusterNodeLabels <"label1(exclusive=true),label2(exclusive=false),label3">]
[-removeFromClusterNodeLabels <label1,label2,label3>] [-replaceLabelsOnNode <"node1[:port]=label1,label2
node2[:port]=label1"> [-failOnUnknownNodes]] [-directlyAccessNodeLabelStore] [-refreshClusterMaxPriority]
[-updateNodeResource [NodeID] [MemSize] [vCores] ([OvercommitTimeout]) or -updateNodeResource
[NodeID] [ResourceTypes] ([OvercommitTimeout])] [-transitionToActive [--forceactive] <serviceId>]
[-transitionToStandby <serviceId>] [-transitionToObserver <serviceId>] [-getServiceState
<serviceId>] [-getAllServiceState] [-checkHealth <serviceId>] [-help [cmd]]

   -refreshQueues: Reload the queues' acls, states and scheduler specific properties. 
		ResourceManager will reload the mapred-queues configuration file.
   -refreshNodes [-g|graceful [timeout in seconds] -client|server]: Refresh the hosts information
at the ResourceManager. Here [-g|graceful [timeout in seconds] -client|server] is optional,
if we specify the timeout then ResourceManager will wait for timeout before marking the NodeManager
as decommissioned. The -client|server indicates if the timeout tracking should be handled
by the client or the ResourceManager. The client-side tracking is blocking, while the server-side
tracking is not. Omitting the timeout, or a timeout of -1, indicates an infinite timeout.
Known Issue: the server-side tracking will immediately decommission if an RM HA failover occurs.
   -refreshNodesResources: 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. 
		ResourceManager will reload the authorization policy file.
   -getGroups [username]: Get the groups which given user belongs to.
   -addToClusterNodeLabels <"label1(exclusive=true),label2(exclusive=false),label3">:
add to cluster node labels. Default exclusivity is true
   -removeFromClusterNodeLabels <label1,label2,label3> (label splitted by ","): remove
from cluster node labels
   -replaceLabelsOnNode <"node1[:port]=label1,label2 node2[:port]=label1,label2"> [-failOnUnknownNodes]
: replace labels on nodes (please note that we do not support specifying multiple labels on
a single host for now.)
		[-failOnUnknownNodes] is optional, when we set this option, it will fail if specified nodes
are unknown.
   -directlyAccessNodeLabelStore: This is DEPRECATED, will be removed in future releases.
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.
   -refreshClusterMaxPriority: Refresh cluster max priority
   -updateNodeResource [NodeID] [MemSize] [vCores] ([OvercommitTimeout]) 
		or
		[NodeID] [resourcetypes] ([OvercommitTimeout]). : Update resource on specific node.
   -transitionToActive [--forceactive] <serviceId>: Transitions the service into Active
state
   -transitionToStandby <serviceId>: Transitions the service into Standby state
   -transitionToObserver <serviceId>: Transitions the service into Observer state
   -getServiceState <serviceId>: Returns the state of the service
   -getAllServiceState: Returns the state of all the services
   -checkHealth <serviceId>: Requests that the service perform a health check.
The HAAdmin tool will exit with a non-zero exit code
if the check fails.
   -help [cmd]: Displays help for the given command or all commands if none is specified.

Generic options supported are:
-conf <configuration file>        specify an application configuration file
-D <property=value>               define a value for a given property
-fs <file:///|hdfs://namenode:port> specify default filesystem URL to use, overrides
'fs.defaultFS' property from configurations.
-jt <local|resourcemanager:port>  specify a ResourceManager
-files <file1,...>                specify a comma-separated list of files to be copied
to the map reduce cluster
-libjars <jar1,...>               specify a comma-separated list of jar files to be
included in the classpath
-archives <archive1,...>          specify a comma-separated list of archives to be unarchived
on the compute machines

The general command line syntax is:
command [genericOptions] [commandOptions]

 
 doesn't include expected messages: 
yarn rmadmin [-refreshQueues] [-refreshNodes [-g|graceful [timeout in seconds] -client|server]]
[-refreshNodesResources] [-refreshSuperUserGroupsConfiguration] [-refreshUserToGroupsMappings]
[-refreshAdminAcls] [-refreshServiceAcl] [-getGroup [username]] [-addToClusterNodeLabels <"label1(exclusive=true),label2(exclusive=false),label3">]
[-removeFromClusterNodeLabels <label1,label2,label3>] [-replaceLabelsOnNode <"node1[:port]=label1,label2
node2[:port]=label1"> [-failOnUnknownNodes]] [-directlyAccessNodeLabelStore] [-refreshClusterMaxPriority]
[-updateNodeResource [NodeID] [MemSize] [vCores] ([OvercommitTimeout]) or -updateNodeResource
[NodeID] [ResourceTypes] ([OvercommitTimeout])] [-transitionToActive [--forceactive] <serviceId>]
[-transitionToStandby <serviceId>] [-getServiceState <serviceId>] [-getAllServiceState]
[-checkHealth <serviceId>] [-help [cmd]]

> TestRMAdminCli#testHelp is failing in trunk
> -------------------------------------------
>
>                 Key: YARN-9178
>                 URL: https://issues.apache.org/jira/browse/YARN-9178
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Abhishek Modi
>            Assignee: Abhishek Modi
>            Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message