Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.2.0
-
None
-
None
Description
Limits were first introduced in 0.20.2xx line with the main goal of protecting jobtracker from rogue jobs. Now that problem no longer exists in yarn, where each job gets its own MR AM. So, its good time now to revisit limits and see which of those still make sense.
Attachments
Issue Links
- requires
-
MAPREDUCE-4443 MR AM and job history server should be resilient to jobs that exceed counter limits
- Patch Available