[
https://issues.apache.org/jira/browse/MAPREDUCE-5856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979035#comment-13979035
]
Robert Kanter commented on MAPREDUCE-5856:
------------------------------------------
Another way of looking at this: if I write the following code in my program:
{code:java}
Configuration conf = new Configuration();
conf.set(...); // Set a bunch of properties or load from some files
JobClient client = new JobClient(conf);
{code}
The expected behavior is that everything {{client}} does will use the
properties I set in {{conf}}. If it doesn't, then that's a bug.
> 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)
