You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/18 19:38:05 UTC
[jira] [Resolved] (MAPREDUCE-443) snapshot a map-reduce to DFS ...
and restore
[ https://issues.apache.org/jira/browse/MAPREDUCE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-443.
----------------------------------------
Resolution: Duplicate
Closing as a dupe of MAPREDUCE-457
> snapshot a map-reduce to DFS ... and restore
> --------------------------------------------
>
> Key: MAPREDUCE-443
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-443
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Reporter: eric baldeschwieler
> Assignee: Owen O'Malley
> Priority: Minor
>
> The idea is to be able to issue a command to the job tracker that
> will halt a map-reduce and archive it to a directory in such a way
> that it can later be restarted.
> We could also set a mode that would cause this to happen to a job
> when it fails. This would allow one to debug and restart a failing
> job reasonably, which might be important, for long running jobs. It
> has certainly been important in similar systems I've seen before. One
> could restart with a new jar or work bench a single failing map or reduce.
--
This message was sent by Atlassian JIRA
(v6.2#6252)