Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-5394

JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.20.0
    • Component/s: None
    • Labels:
      None

      Description

      This can happen when the jobtracker gets restarted more than once. In such cases, the jobtracker depends on the jobhistory file for the next restart count. If the new restart-count is not flushed to the file then there is a fair chance that upon next restart, the jobtracker might schedule a new attempt with an existing id. This can cause problems not only with the side-effect files but also can cause the jobtracker to be in an inconsistent state.

        Attachments

        1. HADOOP-5394-v1.10.1.patch
          25 kB
          Amar Kamat
        2. HADOOP-5394-v1.10.patch
          27 kB
          Amar Kamat
        3. HADOOP-5394-v1.9.1.patch
          26 kB
          Amar Kamat
        4. HADOOP-5394-v1.5.patch
          17 kB
          Amar Kamat
        5. HADOOP-5394-v1.2.patch
          12 kB
          Amar Kamat

          Issue Links

            Activity

              People

              • Assignee:
                amar_kamat Amar Kamat
                Reporter:
                amar_kamat Amar Kamat
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: