[
https://issues.apache.org/jira/browse/MAPREDUCE-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468592#comment-13468592
]
Tom White commented on MAPREDUCE-3936:
--------------------------------------
Luke, are you saying that we should remove the enforcement of limits in AMs,
since the user could choose to do that by modifying the AM themselves?
Perhaps the limits aren't needed in the history server either, since the
Counters objects are short-lived (for display on a web page, or to return to
the job client) so they will be GC'd very quickly. This is unlike the situation
with the JT where all running jobs counters are held in memory for the duration
of the job.
> 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, 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
