[MESOS-2652] Update Mesos containerizer to understand revocable cpu resources

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.23.0
• Labels: twitter
• Epic Link: Oversubscription
• Sprint: Twitter Q2 Sprint 3 - 5/11, Twitter Q2 Sprint 3
• Story Points: 5
• Assignee: Ian Downes
• Reporter: Vinod Kone
• Created: 22/Apr/15 22:23
• Updated: 24/Jul/15 18:03
• Resolved: 29/May/15 21:35

Description

The CPU isolator needs to properly set limits for revocable and non-revocable containers.

The proposed strategy is to use a two-way split of the cpu cgroup hierarchy – normal (non-revocable) and low priority (revocable) subtrees – and to use a biased split of CFS cpu.shares across the subtrees, e.g., a 20:1 split (TBD). Containers would be present in only one of the subtrees. CFS quotas will not be set on subtree roots, only cpu.shares. Each container would set CFS quota and shares as done currently.

Issue Links

• requires: MESOS-2700 Determine CFS behavior with biased cpu.shares subtrees
• requires: MESOS-2701 Implement bi-level cpu.shares subtrees in cgroups/cpu isolator.
• requires: MESOS-2702 Compare split/flattened cgroup hierarchy for CPU oversubscription