Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
None
Description
When the JobTracker detects that its running low on memory it should not expand new jobs if the job has the potential to bring it down. Consider and example where the JobTracker runs on 60% of the max memory and a new job is submitted which can take upto 40% of the max memory. Ideally the JobTracker should queue the job for expansion and expand when sufficient memory is available.
Attachments
Issue Links
- is depended upon by
-
MAPREDUCE-331 Make jobtracker resilient to memory issues
- Resolved