hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4824) Provide a mechanism for jobs to indicate they should not be recovered on restart
Date Thu, 13 Dec 2012 18:20:12 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531271#comment-13531271
] 

Bikas Saha commented on MAPREDUCE-4824:
---------------------------------------

Does it matter if recovered is true if the job conf says dont recover? Please ignore this
comment in case I have not understood the logic correclty :) I am just going by the if condition.
{code}
+    if (recovered && 
+        !job.getJobConf().getBoolean("mapred.job.restart.recover", true)) {
+      return null;
+    }
{code}

Did not quite get the resolution of the defaults.xml issue Harsh referred to earlier. Dont
see any config changes in the last patch.
                
> Provide a mechanism for jobs to indicate they should not be recovered on restart
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4824
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4824
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>          Components: mrv1
>    Affects Versions: 1.1.0
>            Reporter: Tom White
>            Assignee: Tom White
>         Attachments: MAPREDUCE-4824.patch, MAPREDUCE-4824.patch, MAPREDUCE-4824.patch,
MAPREDUCE-4824.patch
>
>
> Some jobs (like Sqoop or HBase jobs) are not idempotent, so should not be recovered on
jobtracker restart. MAPREDUCE-2702 solves this problem for MR2, however the approach there
is not applicable for MR1, since even if we only use the job-level part of the patch and add
a isRecoverySupported method to OutputCommitter, there is no way to use that information from
the JT (which initiates recovery), since the JT does not instantiate OutputCommitters - and
it shouldn't since they are user-level code. (In MR2 it's OK since the MR AM calls the method.)
> Instead, we can add a MR configuration property to say that a job is not recoverable,
and the JT could safely read this from the job conf.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message