[
https://issues.apache.org/jira/browse/MAPREDUCE-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445086#comment-13445086
]
Alejandro Abdelnur commented on MAPREDUCE-3936:
-----------------------------------------------
IMO counters limits should be enforced in the aggregator (JT for Hadoop 1, MRAM
for Hadoop 2). They could be enforced also at Task level as Tom is suggesting,
as a way to stop thing in case of a counters happy task, but only the
aggregator has a full view.
> Clients should not enforce counter limits
> ------------------------------------------
>
> Key: MAPREDUCE-3936
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3936
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: mrv1
> Reporter: Tom White
> Assignee: Tom White
> Attachments: MAPREDUCE-3936.patch
>
>
> The code for enforcing counter limits (from MAPREDUCE-1943) creates a static
> JobConf instance to load the limits, which may throw an exception if the
> client limit is set to be lower than the limit on the cluster (perhaps
> because the cluster limit was raised from the default).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
