[
https://issues.apache.org/jira/browse/HADOOP-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589090#action_12589090
]
Devaraj Das commented on HADOOP-3245:
-------------------------------------
bq. I think we need to work out what is the intended behavior to re-start a job
tracker, and what needs to be persisted to support that behavior.
Agree. This jira is more about being able to save all Job states and being able
to create images that can later be used to recreate the job data structures.
Actually restarting a job would be the next step (a separate jira probably).
This issue is about a framework to enable job restarts.
bq. But at this time, I think it does not sound right to tweak 1876 for some
functionalities we don't have a clear consensus.
Agree and the proposal here doesn't intend to tweak 1876. It could leverage
some APIs from there (just a thought), but at this point it seems like having
edits log kind of a mechanism should work well..
> 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
> Fix For: 0.18.0
>
>
> 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.
