Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
Incompatible change, Reviewed
-
Introduced recovery of jobs when JobTracker restarts. This facility is off by default. Introduced config parameters mapred.jobtracker.restart.recover, mapred.jobtracker.job.history.block.size, and mapred.jobtracker.job.history.buffer.size.
Description
This could probably extend the work done in HADOOP-1876. This feature can be applied for things like jobs being able to survive jobtracker restarts.
Attachments
Attachments
Issue Links
- blocks
-
MAPREDUCE-277 Job history counters should be avaible on the UI.
- Closed
- depends upon
-
HDFS-53 RawLocalFileSystem.listStatus() should not throw FileNotFound exception if a file goes missing while the list is being computed
- Resolved
-
MAPREDUCE-7 Reduce progress in the Reducer crosses 1
- Resolved
-
HADOOP-2403 JobHistory log files contain data that cannot be parsed by org.apache.hadoop.mapred.JobHistory
- Closed
-
HADOOP-3970 Counters written to the job history cannot be recovered back
- Closed
- is blocked by
-
HADOOP-3590 Null pointer exception in JobTracker when the task tracker is not yet resolved
- Closed
-
HADOOP-3947 TaskTrackers fail to connect back upon a re-init action
- Closed
-
HADOOP-3641 Exception while killing the JobTracker
- Closed
-
HADOOP-4112 Got ArrayOutOfBound exception while analyzing the job history
- Closed
-
HADOOP-3780 JobTracker should synchronously resolve the tasktracker's network location when the tracker registers
- Closed
- is depended upon by
-
MAPREDUCE-225 Fault tolerant Hadoop Job Tracker
- Resolved
- is part of
-
HADOOP-3444 Implementing a Resource Manager (V1) for Hadoop
- Resolved
- is related to
-
HADOOP-5436 job history directory grows without bound, locks up job tracker on new job submission
- Resolved
-
HADOOP-4220 Job Restart tests take 10 minutes, can time out very easily
- Closed
- relates to
-
HADOOP-3771 JobClient.runJob() should not kill the job on IOExceptions
- Closed