[
https://issues.apache.org/jira/browse/HADOOP-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-4638:
-------------------------------
Attachment: HADOOP-4638-v1.8.patch
Attaching a new patch. Result of test-patch
{code}
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
{code}
Ant test passes on my box.
> Exception thrown in/from RecoveryManager.recover() should be caught and
> handled
> -------------------------------------------------------------------------------
>
> Key: HADOOP-4638
> URL: https://issues.apache.org/jira/browse/HADOOP-4638
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.20.0
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Priority: Blocker
> Attachments: HADOOP-4638-v1.1.patch, HADOOP-4638-v1.3.patch,
> HADOOP-4638-v1.6.patch, HADOOP-4638-v1.8.patch
>
>
> {{RecoveryManager.recover()}} can throw an exception while recovering a job.
> Since the {{JobTracker}} calls {{RecoveryManager.recover()}} from
> {{offerService()}}, any failure in recovery will cause {{JobTracker}} to
> crash. Ideally the {{RecoveryManager}} should log the failure encountered
> while recovering the job and continue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
