hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1598) Wrongly configured 'hadoop.job.history.user.location' can cause jobs to be pinned in JobTracker's memory forever
Date Sun, 14 Mar 2010 17:13:27 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845110#action_12845110
] 

Hemanth Yamijala commented on MAPREDUCE-1598:
---------------------------------------------

Amar, I don't find this key or the newly mapped key - mapreduce.job.userhistorylocation -
used anywhere in code in trunk. Therefore, I think this bug does not exist for trunk at least
? But we might need fixes for 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.21.0
>            Reporter: Amar Kamat
>            Priority: Blocker
>
> 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.


Mime
View raw message