[ http://issues.apache.org/jira/browse/HADOOP-91?page=comments#action_12371131 ]
eric baldeschwieler commented on HADOOP-91: ------------------------------------------- Good points. Adding an option to specify replication level would be a good addition. Some of this data will be automatically regeneratable, only meta-data may really need high level replication. > snapshot a map-reduce to DFS ... and restore > -------------------------------------------- > > Key: HADOOP-91 > URL: http://issues.apache.org/jira/browse/HADOOP-91 > Project: Hadoop > Type: New Feature > Components: mapred > Reporter: eric baldeschwieler > 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
