You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Robert Chansler (JIRA)" <ji...@apache.org> on 2008/10/21 23:30:44 UTC
[jira] Updated: (HADOOP-3245) Provide ability to persist running
jobs (extend HADOOP-1876)
[ https://issues.apache.org/jira/browse/HADOOP-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Chansler updated HADOOP-3245:
------------------------------------
Release Note: 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. (was: Adds the facility to recover running jobs upon a jobtracker restart i.e jobs can now survive jobtracker restarts. Job's history is used to recover the running jobs. By default the restart mode is turned off. Here are the config parameters that control the recovery
mapred.jobtracker.restart.recover : the recovery switch
mapred.jobtracker.job.history.block.size : block size for the job history file.
mapred.jobtracker.job.history.buffer.size : buffer size for the job history file)
Hadoop Flags: [Incompatible change, Reviewed] (was: [Reviewed, Incompatible change])
> Provide ability to persist running jobs (extend HADOOP-1876)
> ------------------------------------------------------------
>
> Key: HADOOP-3245
> URL: https://issues.apache.org/jira/browse/HADOOP-3245
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Reporter: Devaraj Das
> Assignee: Amar Kamat
> Fix For: 0.19.0
>
> Attachments: HADOOP-3245-v2.5.patch, HADOOP-3245-v2.6.5.patch, HADOOP-3245-v2.6.9.patch, HADOOP-3245-v4.1.patch, HADOOP-3245-v5.13.patch, HADOOP-3245-v5.14.patch, HADOOP-3245-v5.26.patch, HADOOP-3245-v5.30-nolog.patch, HADOOP-3245-v5.31.3-nolog.patch, HADOOP-3245-v5.33.1.patch, HADOOP-3245-v5.35.3-no-log.patch, HADOOP-3245-v5.36-no-log.patch, HADOOP-3245-v5.36.1-no-log.patch, HADOOP-3245-v5.36.2-no-log.patch, HADOOP-3245-v5.36.3-no-log.patch, HADOOP-3245-v5.36.3-no-log.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.