[
https://issues.apache.org/jira/browse/MAPREDUCE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved MAPREDUCE-331.
----------------------------------------
Resolution: Fixed
I'm closing this as fixed. There have been a multitude of parameters added
that help control the JT's memory usage and with YARN, it's harder for end
users to bring the RM down.
> Make jobtracker resilient to memory issues
> ------------------------------------------
>
> Key: MAPREDUCE-331
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-331
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Amar Kamat
>
> JobTracker is vulnerable to memory errors/attacks. Few of them are as follows
> - *JOB INIT :* lot of users submitting large jobs. As every jobs is expanded,
> the jobtracker's memory can be completely used up
> - *JSP :* jsp (jobhistory.jsp etc) can also interfere with jobtracker's
> memory and hence the jobtracker should be protected against such attacks
> - *OLD JOBS :* lot of completed jobs can garble up jobtracker's memory and
> hence should be periodically cleaned up. HADOOP-4766 addresses this.
> The main intention of this issue is to track various jira's that help
> jobtracker battle memory attacks. Jobtracker should always be up and
> available.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
