[
https://issues.apache.org/jira/browse/HADOOP-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626872#action_12626872
]
Amar Kamat commented on HADOOP-3245:
------------------------------------
There is a small bug in the patch.
{code:title=JobHistory.java|borderStyle=solid}
final Pattern historyFilePattern =
Pattern.compile(JOBTRACKER_UNIQUE_STRING + "[0-9]+" + "_"
+ id.toString() + "_" + user + "_" + jobName + "+");
{code}
should be
{code:title=JobHistory.java|borderStyle=solid}
final Pattern historyFilePattern =
Pattern.compile(jobtrackerHostname + "_" + "[0-9]+" + "_"
+ id.toString() + "_" + user + "_" + jobName + "+");
{code}
as {{JOBTRACKER_UNIQUE_STRING}} itself contains a (new) timestamp and hence
_old_ history files wont match the pattern. Will upload a modified patch soon.
> Provide ability to persist running jobs (extend HADOOP-1876)
> ------------------------------------------------------------
>
> Key: HADOOP-3245
> URL: https://issues.apache.org/jira/browse/HADOOP-3245
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Reporter: Devaraj Das
> Assignee: Amar Kamat
> Attachments: HADOOP-3245-v2.5.patch, HADOOP-3245-v2.6.5.patch,
> HADOOP-3245-v2.6.9.patch, HADOOP-3245-v4.1.patch, HADOOP-3245-v5.13.patch,
> HADOOP-3245-v5.14.patch, HADOOP-3245-v5.26.patch,
> HADOOP-3245-v5.30-nolog.patch, HADOOP-3245-v5.31.3-nolog.patch
>
>
> This could probably extend the work done in HADOOP-1876. This feature can be
> applied for things like jobs being able to survive jobtracker restarts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
