[YARN-2154] FairScheduler: Improve preemption to preempt only those containers that would satisfy the incoming request

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 2.4.0
• Component/s: fairscheduler
• Target Version/s: 2.9.0
• Assignee: Arun Suresh
• Reporter: Karthik Kambatla
• Created: 12/Jun/14 05:51
• Updated: 31/Aug/16 03:49
• Resolved: 31/Aug/16 03:45

Description

Today, FairScheduler uses a spray-gun approach to preemption. Instead, it should only preempt resources that would satisfy the incoming request.

Issue Links

• is part of: YARN-4752 FairScheduler should preempt for a ResourceRequest and all preempted containers should be on the same node
• is related to: YARN-4108 CapacityScheduler: Improve preemption to only kill containers that would satisfy the incoming request
• relates to: YARN-3405 FairScheduler's preemption cannot happen between sibling in some case
• relates to: YARN-4134 FairScheduler preemption stops at queue level that all child queues are not over their fairshare