[MAPREDUCE-5582] Setting mapred.job.reduce.memory.mb to 0 from a job with CapacityTracker leads to inconsistent state in JVMManager

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Won't Fix
• Component/s: capacity-sched
• Assignee: Unassigned
• Reporter: Mikhail Davidov
• Created: 13/Oct/13 23:54
• Updated: 09/May/15 00:22
• Resolved: 09/May/15 00:22

Description

If a job sets mapred.job.reduce.memory.mb to 0 the capacity scheduler incorrectly allocates resources eventually causing "Inconsistent state!!! JVM Manager reached an unstable state while reaping a JVM for task" errors from the JVMManager killing all TaskTrackers that have been used for the job.