[
https://issues.apache.org/jira/browse/MAPREDUCE-5856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980059#comment-13980059
]
Karthik Kambatla commented on MAPREDUCE-5856:
---------------------------------------------
bq. One related issue with allowing jobs to increase the default is that it can
blow the memory on the history server which caches recent jobs.
Fair point. To address this in a compatible way, we can add a global max for
the number of counters that the admin can set. We can do this in a separate
JIRA.
> Counter limits always use defaults even if JobClient is given a different
> Configuration
> ---------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5856
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5856
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Affects Versions: 2.3.0, 2.4.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: MAPREDUCE-5856.patch
>
>
> If you have a job with more than the default number of counters (i.e. > 120),
> and you create a JobClient with a Configuration where the default is
> increased (e.g. 500), then JobClient will throw this Exception:
> {noformat}
> org.apache.hadoop.mapreduce.counters.LimitExceededException: Too many
> counters: 121 max=120
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
