[
https://issues.apache.org/jira/browse/MAPREDUCE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726783#action_12726783
]
Ramya R commented on MAPREDUCE-130:
-----------------------------------
The above fix does not work in one special case. When a job completes and
before it retires, if the JT is restarted, the conf files are not deleted from
the the logdir. This will still lead to accumulation of conf files in the
logdir of all those jobs which were completed but not yet retired when the JT
was restarted. The issue is more pronounced when " retirejob interval" is very
high
> Delete the jobconf copy from the log directory of the JobTracker when the job
> is retired
> ----------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-130
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-130
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Devaraj Das
> Assignee: Amar Kamat
> Fix For: 0.20.1
>
> Attachments: HADOOP-5995-v1.0.patch, HADOOP-5995-v1.1.patch,
> MAPREDUCE-130-v1.0-branch-0.20.patch, MAPREDUCE-130-v1.0.patch
>
>
> The JobTracker (for web-ui viewing purposes), copies the jobconf from the
> hdfs and store it in the log directory. The file should be deleted when the
> job is retired (removed from memory).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
