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

default rm/am expire interval should not be smaller than default resourcemanager connect wait time

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

    Details

    • Type: Bug
    • Status: Patch Available
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: client
    • Labels:

      Description

      take am for example, if am can't connect to RM, after am expire (600s), RM relaunch am, and there will be two am at the same time util resourcemanager connect max wait time(900s) passed.

      DEFAULT_RESOURCEMANAGER_CONNECT_MAX_WAIT_MS = 15 * 60 * 1000;
      DEFAULT_RM_AM_EXPIRY_INTERVAL_MS = 600000;
      DEFAULT_RM_NM_EXPIRY_INTERVAL_MS = 600000;

        Attachments

        1. YARN-3518.001.patch
          0.9 kB
          sandflee
        2. YARN-3518.002.patch
          14 kB
          sandflee
        3. YARN-3518.003.patch
          14 kB
          sandflee
        4. YARN-3518.004.patch
          15 kB
          sandflee

        Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. YARN-3554 Default value for maximum nodemanager connect wait time is too high

        • Major - Major loss of function.
        • Closed

          Activity
          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              sandflee sandflee
              Reporter:
              sandflee sandflee

              Dates

              • Created:
                Updated:

                Issue deployment