[YARN-4779] Fix AM container allocation logic in SLS

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha4
• Component/s: scheduler-load-simulator
• Labels: oct16-medium
• Hadoop Flags: Reviewed
• Assignee: Wangda Tan
• Reporter: Wangda Tan
• Created: 08/Mar/16 23:01
• Updated: 24/Feb/17 17:45
• Resolved: 24/Feb/17 16:12

Description

Currently, SLS uses unmanaged AM for simulated map-reduce applications. And first allocated container for each app is considered to be the master container.

This could be problematic when preemption happens. CapacityScheduler preempt AM container at lowest priority, but the simulated AM container isn't recognized by scheduler – it is a normal container from scheduler's perspective.

This JIRA tries to fix this logic: do the real AM allocation instead of using unmanaged AM.