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

Inconsistency between JT/TT for tasks taking a long time to launch

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

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 1.2.1
    • 1.3.0
    • jobtracker, tasktracker
    • None
    • Reviewed

    Description

      For the tasks that take too long to launch (for genuine reasons like large distributed caches), JT expires the task. Depending on whether job recovery is enabled and the JT's restart state, another attempt is launched or not even when the JT is not restarted. The status of the attempt changes to "Error launching task". Meanwhile, the TT is not informed of this task expiry and eventually launches the task. Also, the "new" attempt might be assigned to the same TT leading to more inconsistent behavior.

      To avoid this, one can bump up the mapred.tasktracker.expiry.interval, but leading to long TT failure discovery times.

      We should have a per-job timeout for task launches/ heartbeat and JT/TT should be consistent in what they say.

      Attachments

        1. repro-mr-5877.patch
          1 kB
          Karthik Kambatla
        2. mr-5877-1.patch
          2 kB
          Karthik Kambatla

        Activity

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

          People

            kasha Karthik Kambatla
            kasha Karthik Kambatla
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment