Uploaded image for project: 'Hadoop Map/Reduce'
  1. Hadoop Map/Reduce
  2. MAPREDUCE-6697

Concurrent task limits should only be applied when necessary

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.7.0
    • 2.9.0, 2.7.4, 3.0.0-alpha4, 2.8.2
    • mrv2
    • None
    • Reviewed

    Description

      The concurrent task limit feature should only adjust the ANY portion of the AM heartbeat ask when a limit is truly necessary, otherwise extraneous containers could be allocated by the RM to the AM adding some overhead to both. Specifying a concurrent task limit that is beyond the total number of tasks in the job should be the same as asking for no limit.

      Attachments

        1. MAPREDUCE-6697-branch-2.7.001.patch
          7 kB
          Konstantin Shvachko
        2. MAPREDUCE-6697-branch-2.8.001.patch
          7 kB
          Nathan Roberts
        3. MAPREDUCE-6697-v1.patch
          7 kB
          Nathan Roberts

        Issue Links

        Activity

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

          People

            nroberts Nathan Roberts
            jlowe Jason Darrell Lowe
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment