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 "Owen O'Malley (JIRA)" <ji...@apache.org> on 2011/01/20 04:25:47 UTC
[jira] Updated: (MAPREDUCE-1598) Wrongly configured
'hadoop.job.history.user.location' can cause jobs to be pinned in
JobTracker's memory forever
[ https://issues.apache.org/jira/browse/MAPREDUCE-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Owen O'Malley updated MAPREDUCE-1598:
-------------------------------------
Fix Version/s: (was: 0.20.3)
> Wrongly configured 'hadoop.job.history.user.location' can cause jobs to be pinned in JobTracker's memory forever
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1598
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1598
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.20.1
> Reporter: Amar Kamat
> Attachments: mapred-1598
>
>
> Wrongly configured 'hadoop.job.history.user.location' can disable job-history. Jobs retires when JobHistory notifies the JobTracker after moving the history file to the done folder (i.e mapreduce.jobtracker.jobhistory.completed.location). If the JobHistory gets disabled, JobTracker would not receive any notification and thus jobs will be pinned in JobTracker's memory forever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.