[
https://issues.apache.org/jira/browse/MAPREDUCE-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated MAPREDUCE-3469:
-------------------------------------
Target Version/s: 0.22.0
Fix Version/s: (was: 0.20.203.0)
Assignee: Konstantin Shvachko (was: Mahadev konar)
Konstantin - you might want to port this to 0.22 too. I'll assign it to you for
now... please take a look. Thanks.
> Port to 0.22 - Implement limits on per-job JobConf, Counters, StatusReport,
> Split-Sizes
> ---------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-3469
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3469
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Mahadev konar
> Assignee: Konstantin Shvachko
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
