[HADOOP-5394] JobTracker might schedule 2 attempts of the same task with the same attempt id across restarts

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.20.0
• Assignee: Amar Kamat
• Reporter: Amar Kamat
• Created: 04/Mar/09 13:34
• Updated: 08/Jul/09 16:53
• Resolved: 08/Apr/09 12:55

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.

Issue Links

• is blocked by: HADOOP-5521 Remove dependency of testcases on RESTART_COUNT