[
https://issues.apache.org/jira/browse/MAPREDUCE-2427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035627#comment-13035627
]
Todd Lipcon commented on MAPREDUCE-2427:
----------------------------------------
Hi Devaraj. This patch seems to address the case where the "history" location
is a file at startup. But, if I understand Sammer correctly, the problem here
is when users do something like rm -Rf the history/ directory while the JT is
running. Then, next time (and all future times) that a file is moving into the
history dir, it ends up replacing this file.
So, I think we need to change the place where the file gets renamed so that it
checks/mkdirs the history/ directory first.
> JT should ensure history directory is a directory
> -------------------------------------------------
>
> Key: MAPREDUCE-2427
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2427
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.20.2
> Reporter: E. Sammer
> Assignee: Devaraj K
> Fix For: 0.20.4, 0.23.0
>
> Attachments: MAPREDUCE-2427.0.20.patch, MAPREDUCE-2427.patch
>
>
> If the JT history directory doesn't exist or isn't a directory retired job
> files are renamed to a file called 'history' and eventually start overwriting
> each other. The JT should ensure 'history' exists and is a directory before
> performing the move.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira