[MESOS-8938] Improve the allocator so that it does not send cpu only or mem only resources in certain cases

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: allocation
• Assignee: Unassigned
• Reporter: Vinod Kone
• Shepherd: Benjamin Mahler
• Created: 19/May/18 01:15
• Updated: 19/May/18 01:17

Description

MESOS-1688 changed the allocator behavior so that it can offer cpu only or memory only resources to frameworks, but this is not always useful. For example, if a framework has never launched an executor/container on an agent, it doesn't make sense to send it a cpu only or memory only offer. Once a framework launches an executor, it could use cpu only or memory only offers to grow the size of the executor.

This ticket tracks an improvement to the "isAllocatable()" function to make it more smart as discussed above. This is important to improve pathological situations like MESOS-8935.

Issue Links

• relates to: MESOS-8935 Quota limit "chopping" can lead to cpu-only and memory-only offers.