[MAPREDUCE-2876] ContainerAllocationExpirer appears to use the incorrect configs

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.23.0
• Fix Version/s: 0.23.0
• Component/s: mrv2
• Target Version/s: 0.23.0
• Assignee: Anupam Seth
• Reporter: Robert Joseph Evans
• Created: 24/Aug/11 20:12
• Updated: 15/Nov/11 00:48
• Resolved: 10/Oct/11 03:07

Description

ContainerAllocationExpirer sets the expiration interval to be RMConfig.CONTAINER_LIVELINESS_MONITORING_INTERVAL but uses AMLIVELINESS_MONITORING_INTERVAL as the interval. This is very different from what AMLivelinessMonitor does.

There should be two configs RMConfig.CONTAINER_LIVELINESS_MONITORING_INTERVAL for the monitoring interval and RMConfig.CONTAINER_EXPIRY_INTERVAL for the expiry.

Issue Links

• is blocked by: MAPREDUCE-2864 Renaming of configuration property names in yarn