Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.21.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Removed the Job Retire thread and the associated configuration parameters. Job is purged from memory as soon as the history file is copied to HDFS. Only JobStatus object is retained in the retired jobs cache.

      Description

      Currently completed job's full data structures are kept in memory based on mapred.jobtracker.completeuserjobs.maximum, mapred.jobtracker.retirejob.interval.min, mapred.jobtracker.retirejob.interval and mapred.jobtracker.retirejob.check settings. These controls are not much useful now since MAPREDUCE-817 introduced a cache for keeping just the very basic info of the completed job. These settings should be removed and the job should be purged as soon as the history files are available in HDFS.
      Going forward, clients can read the history files if they need to drill down into more information (MAPREDUCE-864).

      1. 870_v3.patch
        30 kB
        Sharad Agarwal
      2. 870_v2.patch
        28 kB
        Sharad Agarwal
      3. 870_v1.patch
        27 kB
        Sharad Agarwal

        Issue Links

          Activity

          Tom White made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Amareshwari Sriramadasu made changes -
          Link This issue relates to MAPREDUCE-1920 [ MAPREDUCE-1920 ]
          Sharad Agarwal made changes -
          Status Patch Available [ 10002 ] Resolved [ 5 ]
          Hadoop Flags [Reviewed]
          Release Note Removed the Job Retire thread and the associated configuration parameters. Job is purged from memory as soon as the history file is copied to HDFS. Only JobStatus object is retained in the retired jobs cache.
          Fix Version/s 0.21.0 [ 12314045 ]
          Resolution Fixed [ 1 ]
          Sharad Agarwal made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Sharad Agarwal made changes -
          Attachment 870_v3.patch [ 12417097 ]
          Sharad Agarwal made changes -
          Status Patch Available [ 10002 ] Open [ 1 ]
          Sharad Agarwal made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Sharad Agarwal made changes -
          Status Patch Available [ 10002 ] Open [ 1 ]
          Sharad Agarwal made changes -
          Summary Purge the completed job from memory as soon as the history file is copied in to HDFS Clean up the job Retire code
          Sharad Agarwal made changes -
          Attachment 870_v2.patch [ 12416751 ]
          Sharad Agarwal made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Sharad Agarwal made changes -
          Attachment 870_v1.patch [ 12416552 ]
          Sharad Agarwal made changes -
          Field Original Value New Value
          Description Currently completed job's full data structures are kept in memory based on mapred.jobtracker.completeuserjobs.maximum, mapred.jobtracker.retirejob.interval.min, mapred.jobtracker.retirejob.interval and mapred.jobtracker.retirejob.check settings. These controls are not much useful now since MAPREDUCE-817 introduced a cache for keeping just the very basic info of the completed job. These settings should be removed and the job should be purged as soon as the history files are available in HDFS.
          Going forward, clients can read the history files if they need to drill down into more information (MAPREDUCE-864).
          Sharad Agarwal created issue -

            People

            • Assignee:
              Sharad Agarwal
              Reporter:
              Sharad Agarwal
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development