[HADOOP-3842] There is a window where the JobTracker is in the RUNNING state (i.e ready to accept jobs) and never executes them.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.20.0
• Assignee: Hemanth Yamijala
• Reporter: Amar Kamat
• Created: 28/Jul/08 06:56
• Updated: 08/Jul/09 16:52
• Resolved: 25/Oct/08 11:48

Description

Prior to HADOOP-3412, job tracker could accept jobs without even offering service (i.e without JobTracker.offerService() being called). In such a case the job stays in JT's memory and job execution was guaranteed. With HADOOP-3412, JobTracker.submitJob() adds the job to JT's local structures and passes it to the scheduler. Scheduler gets initialized in JobTracker.offerService() and hence calling JobTracker.submitJob() before calling JobTracker.offerService() is actually a no-op. The job stays in JT's memory but never gets initialized. This is

• backward incompatible
• erroneous as there is a window where the jobtracker is ready to accept jobs, accepts them and never executes them.