[MAPREDUCE-4311] Capacity scheduler.xml does not accept decimal values for capacity and maximum-capacity settings

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.23.3
• Fix Version/s: 0.23.3, 2.0.2-alpha
• Component/s: capacity-sched, mrv2
• Target Version/s: 0.23.3
• Hadoop Flags: Incompatible change, Reviewed
• Assignee: Karthik Kambatla
• Reporter: Thomas Graves
• Created: 04/Jun/12 18:08
• Updated: 03/Nov/14 18:05
• Resolved: 19/Jun/12 13:10

Description

if capacity scheduler capacity or max capacity set with decimal it errors:

• Error starting ResourceManager

java.lang.NumberFormatException: For input string: "10.5"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:458)
at java.lang.Integer.parseInt(Integer.java:499)
at org.apache.hadoop.conf.Configuration.getInt(Configuration.java:713)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerConfiguration.getCapacity(CapacitySchedulerConfiguration.java:147)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.<init>(LeafQueue.java:147)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.parseQueue(CapacityScheduler.java:297)
at

0.20 used to take decimal and this could be an issue on large clusters that would have queues with small allocations.

Issue Links

• is depended upon by: MAPREDUCE-4341 add types to capacity scheduler properties documentation