hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1598) Wrongly configured 'hadoop.job.history.user.location' can cause jobs to be pinned in JobTracker's memory forever
Date Mon, 15 Mar 2010 04:11:27 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Amareshwari Sriramadasu updated MAPREDUCE-1598:

    Affects Version/s:     (was: 0.21.0)
        Fix Version/s:     (was: 0.21.0)

"Disabling job history if anything fails" is not present in branch 0.21 or trunk. It is removed
in job history refactoring through MAPREDUCE-157. Even the configuration mapreduce.jobtracker.jobhistory.completed.location
is removed in the same jira.
So, the bug is present in 0.20.* and earlier versions.

> 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
>            Priority: Blocker
>             Fix For: 0.20.3
> 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.

View raw message