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

Allow jobtracker to be configured with zero completed jobs in memory

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.21.0
    • None
    • None
    • Reviewed
    • Hide
      If the number of jobs per user exceeded mapred.jobtracker.completeuserjobs.maximum then the job was flushed out of the jobtracker's memory after the job finishes min-time (hardcoded to 1 min). This caused jobclient's fail with NPE. In this patch the min-time to retain a job is made configurable (mapred.jobtracker.retirejob.interval.min).
      Show
      If the number of jobs per user exceeded mapred.jobtracker.completeuserjobs.maximum then the job was flushed out of the jobtracker's memory after the job finishes min-time (hardcoded to 1 min). This caused jobclient's fail with NPE. In this patch the min-time to retain a job is made configurable (mapred.jobtracker.retirejob.interval.min).

    Description

      There is no way to specify that the jobtracker should not keep any completed job in memory.

      Attachments

        1. MAPREDUCE-502-v1.1-branch-0.20-example.2.patch
          7 kB
          Amar Kamat
        2. MAPREDUCE-502-v1.1.patch
          11 kB
          Amar Kamat
        3. MAPREDUCE-502-v1.0.patch
          11 kB
          Amar Kamat
        4. HADOOP-4973-v2.2.patch
          11 kB
          Amar Kamat
        5. HADOOP-4973-v2.1.patch
          10 kB
          Amar Kamat

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: