[MAPREDUCE-5856] Counter limits always use defaults even if JobClient is given a different Configuration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.3.0, 2.4.0
• Component/s: client
• Assignee: Robert Kanter
• Reporter: Robert Kanter
• Created: 23/Apr/14 22:18
• Updated: 08/May/14 17:07
• Resolved: 08/May/14 17:07

Description

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:

org.apache.hadoop.mapreduce.counters.LimitExceededException: Too many counters: 121 max=120

Issue Links

• duplicates: MAPREDUCE-5875 Make Counter limits consistent across JobClient, MRAppMaster, and YarnChild
• is related to: MAPREDUCE-5875 Make Counter limits consistent across JobClient, MRAppMaster, and YarnChild