[
https://issues.apache.org/jira/browse/HADOOP-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620175#action_12620175
]
Amar Kamat commented on HADOOP-3245:
------------------------------------
bq. 1) This approach/patch works fine with history on local fs. With history on
HDFS, the history file becomes visible but not available (i.e file-size = 0).
The file becomes available only on close(). Sync() documentation indicates that
the file-data availability is not guaranteed.
The recently uploaded patch makes the block size of the history-file
configurable. The parameter to change it is
{{mapred.jobtracker.job.history.block.size}} (in bytes). For testing it, I
started a small job on a single node cluster with history-block-size as {{1k}}.
It seems to work fine and the history file is now visible and available. With
respect to the {{zero-size-file}}, I think we are ok to lose some small amount
of information.
> 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
>
>
> 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.
