Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-666 [Umbrella] Support rolling upgrades in YARN
  3. YARN-819

ResourceManager and NodeManager should check for a minimum allowed version

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.0.4-alpha
    • 2.3.0
    • None

    Description

      Our use case is during upgrade on a large cluster several NodeManagers may not restart with the new version. Once the RM comes back up the NodeManager will re-register without issue to the RM.

      The NM should report the version the RM. The RM should have a configuration to disallow the check (default), equal to the RM (to prevent config change for each release), equal to or greater than RM (to allow NM upgrades), and finally an explicit version or version range.

      The RM should also have an configuration on how to treat the mismatch: REJECT, or REBOOT the NM.

      Attachments

        1. YARN-819-1.patch
          26 kB
          Robert Parker
        2. YARN-819-2.patch
          26 kB
          Robert Parker
        3. YARN-819-3.patch
          26 kB
          Robert Parker

        Issue Links

        Activity

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

          People

            robsparker Robert Parker
            robsparker Robert Parker
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Issue deployment