[
https://issues.apache.org/jira/browse/MAPREDUCE-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krishna Ramachandran updated MAPREDUCE-1598:
--------------------------------------------
Attachment: mapred-1598
like it has been pointed out, this has been fixed in trunk and addressed in an
internal version via mapreduce-1699 this is no longer a blocker?
(optionally we can port to 1699 to 20.x)
In addition we can do a simple permission check (see attachment) in trunk?
> 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
>
> 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.
