[MAPREDUCE-331] Make jobtracker resilient to memory issues

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Assignee: Unassigned
• Reporter: Amar Kamat
• Created: 02/Jan/09 08:28
• Updated: 21/Jul/14 17:53
• Resolved: 21/Jul/14 17:53

Description

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.

Issue Links

• depends upon: MAPREDUCE-1500 Improve the way Counters are managed by JobTracker
• depends upon: MAPREDUCE-1316 JobTracker holds stale references to retired jobs via unreported tasks
• depends upon: MAPREDUCE-1422 Changing permissions of files/dirs under job-work-dir may be needed sothat cleaning up of job-dir in all mapred-local-directories succeeds always
• depends upon: MAPREDUCE-289 JobTracker should not expand jobs if its running low on memory
• incorporates: MAPREDUCE-177 Hadoop performance degrades significantly as more and more jobs complete
• incorporates: MAPREDUCE-291 Optionally a separate daemon should serve JobHistory