[
https://issues.apache.org/jira/browse/MAPREDUCE-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated MAPREDUCE-4610:
---------------------------------
Attachment: MAPREDUCE-4610.patch
Here's a patch that fixes this. I tested it manually by starting a cluster and
running a job that creates more than the default number of counters (120). When
I increased mapreduce.job.counters.limit beyond that number I didn't see any
counter limit exception.
Writing a unit test is actually difficult since the limits are loaded
statically. I'd like to fix that as a part of fixing the client-side limit
enforcement problem in MAPREDUCE-3936. But I think this is useful to go in as a
compatibility fix first.
> Support deprecated mapreduce.job.counters.limit property in MR2
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-4610
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4610
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 2.0.0-alpha
> Reporter: Tom White
> Assignee: Tom White
> Attachments: MAPREDUCE-4610.patch
>
>
> The property mapreduce.job.counters.limit was introduced in MAPREDUCE-1943,
> but the mechanism was changed in MAPREDUCE-901 where the property name was
> changed to mapreduce.job.counters.max without supporting the old name. We
> should deprecate but honour the old name to make it easier for folks to move
> from Hadoop 1 to Hadoop 2.
--
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
