[
https://issues.apache.org/jira/browse/MAPREDUCE-5856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated MAPREDUCE-5856:
-------------------------------------
Attachment: MAPREDUCE-5856.patch
The fix is very simple; we just need to call {{Limits.init(...)}} from
{{JobClient.init(...)}}.
I couldn't do a unit test because the Configuration used by Limits is only
loaded once, but I did verify that it fixes the problem and the fix is pretty
trivial.
> 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)
