You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2009/06/11 22:00:08 UTC
[jira] Commented: (HADOOP-4372) Improve the way the job history
files are managed during job recovery
[ https://issues.apache.org/jira/browse/HADOOP-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718606#action_12718606 ]
Hudson commented on HADOOP-4372:
--------------------------------
Integrated in Hadoop-trunk #863 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/863/])
> 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
> Fix For: 0.21.0
>
> 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.