[MAPREDUCE-4936] JobImpl uber checks for cpu are wrong

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.3-alpha
• Fix Version/s: 2.0.3-alpha
• Component/s: mrv2
• Target Version/s: 2.0.3-alpha
• Hadoop Flags: Reviewed
• Assignee: Arun Murthy
• Reporter: Daryn Sharp
• Created: 11/Jan/13 16:57
• Updated: 15/Feb/13 13:09
• Resolved: 15/Jan/13 14:49

Description

The cpu checks for uberizing have two issues:

1. the defaults are hardcoded instead of using the conf defaults
2. the comparison against the sys cpu size is using < instead of <=

    boolean smallCpu =
        (
            Math.max(
                conf.getInt(MRJobConfig.MAP_CPU_VCORES, 1), 
                conf.getInt(MRJobConfig.REDUCE_CPU_VCORES, 1)) < 
             sysCPUSizeForUberSlot
        );

Everything is defaulting to 1, so uber cpu checks are now disabled causing TestUberAM to fail.

Issue Links

• is broken by: MAPREDUCE-4520 Add experimental support for MR AM to schedule CPUs along-with memory