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

Default value for maximum nodemanager connect wait time is too high

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

    Details

    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      The default value for yarn.client.nodemanager-connect.max-wait-ms is 900000 msec or 15 minutes, which is way too high. The default container expiry time from the RM and the default task timeout in MapReduce are both only 10 minutes.

        Attachments

        1. YARN-3554.20150429-1.patch
          2 kB
          Naganarasimha G R
        2. YARN-3554-20150429-2.patch
          2 kB
          Naganarasimha G R

        Issue Links

        is related to

        Bug - A problem which impairs or prevents the functions of the product. YARN-3238 Connection timeouts to nodemanagers are retried at multiple levels

        • Blocker - Blocks development and/or testing work, production could not run
        • Closed

        Bug - A problem which impairs or prevents the functions of the product. HADOOP-11398 RetryUpToMaximumTimeWithFixedSleep needs to behave more accurately

        • Major - Major loss of function.
        • Patch Available

        Bug - A problem which impairs or prevents the functions of the product. YARN-3518 default rm/am expire interval should not be smaller than default resourcemanager connect wait time

        • Major - Major loss of function.
        • Patch Available

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

            People

            • Assignee:
              Naganarasimha Naganarasimha G R
              Reporter:
              jlowe Jason Darrell Lowe

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment