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

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

    Details

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

      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.

        Attachments

          Activity

            People

            • Assignee:
              yhemanth Hemanth Yamijala
              Reporter:
              amar_kamat Amar Kamat
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: