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

Prior code fix in Capacity Scheduler prevents speculative execution in jobs

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • None
    • None

    Description

      As part of the code fix for HADOOP-4035, the Capacity Scheduler obtains a task from JobInProgress (calling obtainNewMapTask() or obtainNewReduceTask()) only if the number of pending tasks for a job is greater than zero (see the if-block in TaskSchedulingMgr.getTaskFromJob()). So, if a job has no pending tasks and only has running tasks, it will never be given a slot, and will never have a chance to run a speculative task.

      Attachments

        1. HADOOP-4981-5-br20.patch
          29 kB
          Sreekanth Ramakrishnan
        2. HADOOP-4981-5.patch
          28 kB
          Sreekanth Ramakrishnan
        3. HADOOP-4981-4.patch
          28 kB
          Sreekanth Ramakrishnan
        4. HADOOP-4981-3.patch
          25 kB
          Sreekanth Ramakrishnan
        5. HADOOP-4981-2.patch
          24 kB
          Sreekanth Ramakrishnan
        6. HADOOP-4981-1.patch
          17 kB
          Sreekanth Ramakrishnan
        7. 4981.2.patch
          28 kB
          Vivek Ratan
        8. 4981.1.patch
          26 kB
          Vivek Ratan

        Activity

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

          People

            sreekanth Sreekanth Ramakrishnan
            vivekr Vivek Ratan
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment