You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Eric Payne (JIRA)" <ji...@apache.org> on 2014/04/10 19:36:25 UTC
[jira] [Commented] (MAPREDUCE-5267) History server should be more
robust when cleaning old jobs
[ https://issues.apache.org/jira/browse/MAPREDUCE-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965582#comment-13965582 ]
Eric Payne commented on MAPREDUCE-5267:
---------------------------------------
[~maysamyabandeh] and [~jlowe]
The patch does fail to apply, as the above comment says, but it is just the patch for TestJobHistoryParsing.java, which could probably be easily fixed.
Is this issue still a problem? I doubt it will be fixed in 0.23, so if it's still a problem, can we remove the 0.23.11 target and leave it targeted for 3.0.0?
> History server should be more robust when cleaning old jobs
> -----------------------------------------------------------
>
> Key: MAPREDUCE-5267
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5267
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobhistoryserver
> Affects Versions: 0.23.7, 2.0.4-alpha
> Reporter: Jason Lowe
> Assignee: Maysam Yabandeh
> Attachments: MAPREDUCE-5267.patch, MAPREDUCE-5267.patch
>
>
> Ran across a situation where an admin user had accidentally created a directory in one of the date directories under /mapred/history/done/ that was not readable by the historyserver user. That effectively prevented the history server from cleaning any jobs from that date forward, as it hit an IOException trying to scan the directory and that aborted the entire clean process.
> The history server should localize IOException handling to the directory/file being processed and move on to the next entry in the list rather than aborting the entire cleaning process.
--
This message was sent by Atlassian JIRA
(v6.2#6252)