Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
We have come across issues in production clusters wherein users abuse counters, statusreport messages and split sizes. One such case was when one of the users had 100 million counters. This leads to jobtracker going out of memory and being unresponsive. In this jira I am proposing to put sane limits on the status report length, the number of counters and the size of block locations returned by the input split.
Attachments
Attachments
Issue Links
- is cloned by
-
MAPREDUCE-3469 Port to 0.22 - Implement limits on per-job JobConf, Counters, StatusReport, Split-Sizes
- Resolved
- relates to
-
MAPREDUCE-5186 mapreduce.job.max.split.locations causes some splits created by CombineFileInputFormat to fail
- Closed