[
https://issues.apache.org/jira/browse/HADOOP-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626859#action_12626859
]
Hemanth Yamijala commented on HADOOP-3245:
------------------------------------------
bq. Note that a working solution for HADOOP-3970 is present in this patch too.
I think it is better to submit the solution of HADOOP-3970 as part of that
JIRA, rather than including it in this patch. If I understand correctly,
without this fix, everything except counters will be recovered for running jobs
on a restart. Probably HADOOP-3970 should block this and get committed first.
Also, I think it will be good to have a configuration variable to disable job
recovery. This is to provide backwards compatibility, and also gives a way to
disable this feature if required.
> 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
> 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
>
>
> 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.
