Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-149 [Umbrella] ResourceManager (RM) Fail-over
  3. YARN-2807

Option "--forceactive" not works as described in usage of "yarn rmadmin -transitionToActive"

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 2.7.0
    • None
    • Reviewed

    Description

      Currently the help message of "yarn rmadmin -transitionToActive" is:

      transitionToActive: incorrect number of arguments
      Usage: HAAdmin [-transitionToActive <serviceId> [--forceactive]]
      

      But the --forceactive not works as expected. When transition RM state with --forceactive:

      yarn rmadmin -transitionToActive rm2 --forceactive
      Automatic failover is enabled for org.apache.hadoop.yarn.client.RMHAServiceTarget@64c9f31e
      Refusing to manually manage HA state, since it may cause
      a split-brain scenario or other incorrect state.
      If you are very sure you know what you are doing, please
      specify the forcemanual flag.
      

      As shown above, we still cannot transitionToActive when automatic failover is enabled with --forceactive.

      The option can work is: --forcemanual, there's no place in usage describes this option. I think we should fix this

      Attachments

        1. YARN-2807.4.patch
          7 kB
          Masatake Iwasaki
        2. YARN-2807.3.patch
          7 kB
          Masatake Iwasaki
        3. YARN-2807.2.patch
          7 kB
          Masatake Iwasaki
        4. YARN-2807.1.patch
          3 kB
          Masatake Iwasaki

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            iwasakims Masatake Iwasaki
            leftnoteasy Wangda Tan
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment