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 "Devaraj Das (JIRA)" <ji...@apache.org> on 2009/04/17 13:19:15 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=12700130#action_12700130 ]
Devaraj Das commented on HADOOP-4372:
-------------------------------------
Could we instead pass a boolean to logSubmitted depending on the restart-count value (0 == new job, and the boolean is true), and then create the recovery file inside the jobHistory if the boolean is false.
The problem with the current patch is that the filename of the history file changes upon restart..
> 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
>
>
> 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.