[
https://issues.apache.org/jira/browse/HADOOP-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amar Kamat updated HADOOP-4372:
-------------------------------
Attachment: HADOOP-4372-v3.1.patch
Attaching a patch that optimizes jobhistory for new jobs. 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 doesn't appear to include any new
or modified tests.
[exec] Please justify why no tests are needed for
this patch.
[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 passed on my box
> Improve the way the job history files are managed during job recovery
> ---------------------------------------------------------------------
>
> Key: HADOOP-4372
> URL: https://issues.apache.org/jira/browse/HADOOP-4372
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Amar Kamat
> Assignee: Amar Kamat
> Attachments: HADOOP-4372-v1.4.patch, HADOOP-4372-v1.patch,
> HADOOP-4372-v3.0.patch, HADOOP-4372-v3.1.patch
>
>
> Today we use the _.recover_ technique to handle the job history files when
> the jobtracker restarts. The comment
> [here|https://issues.apache.org/jira/browse/HADOOP-3245?focusedCommentId=12629080#action_12629080]
> proposes a better way to handle the files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
