Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-9985

Unsupported "transitionToObserver" option displaying for rmadmin command

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.2.1
    • Fix Version/s: 3.3.0, 3.2.2
    • Component/s: RM, yarn
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      Unsupported "transitionToObserver" option displaying for rmadmin command

      Check the options for Yarn rmadmin command
      It will display the "-transitionToObserver <serviceId>" option which is not supported
      by yarn rmadmin command which is wrong behavior.
      But if you check the yarn rmadmin -help it will not display any option  "-transitionToObserver <serviceId>"

       

       

      ==========================

      install/hadoop/resourcemanager/bin> ./yarn rmadmin -help
      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>] [-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
      -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.

       

       

      ==========================

       

       

        Attachments

        1. image-2019-11-18-18-31-17-755.png
          94 kB
          Souryakanta Dwivedy
        2. image-2019-11-18-18-35-54-688.png
          22 kB
          Souryakanta Dwivedy
        3. YARN-9985-01.patch
          4 kB
          Ayush Saxena
        4. YARN-9985-02.patch
          7 kB
          Ayush Saxena

        Issue Links

          Activity

            People

            • Assignee:
              ayushtkn Ayush Saxena
              Reporter:
              SouryakantaDwivedy Souryakanta Dwivedy

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment