[MESOS-1807] Disallow executors with cpu only or memory only resources

• Type: Improvement
• Status: Accepted
• Priority: Major
• Resolution: Unresolved
• Sprint: Twitter Q4 Sprint 1, Twitter Mesos Q4 Sprint 2, Twitter Mesos Q4 Sprint 3
• Story Points: 3
• Assignee: Unassigned
• Reporter: Vinod Kone
• Shepherd: Benjamin Mahler
• Created: 17/Sep/14 18:31
• Updated: 21/Jan/20 19:59

Description

Currently master allows executors to be launched with either only cpus or only memory but we shouldn't allow that.
This is because executor is an actual unix process that is launched by the slave. If an executor doesn't specify cpus, what should the cpu limits be for that executor when there are no tasks running on it? If no cpu limits are set then it might starve other executors/tasks on the slave violating isolation guarantees. Same goes with memory. Moreover, the current containerizer/isolator code will throw failures when using such an executor, e.g., when the last task on the executor finishes and Containerizer::update() is called with 0 cpus or 0 mem.

According to a source code TODO this should also include checking whether requested resources are greater than MIN_CPUS/MIN_BYTES.

Issue Links

• is blocked by: MESOS-1718 Command executor can overcommit the agent.
• is related to: AURORA-1246 Mesos warns about executor resources being to small
• relates to: MESOS-4419 DEFAULT_EXECUTOR_INFO's CPU/MEM is none in Mesos Tests
• relates to: MESOS-7197 Requesting tiny amount of CPU crashes master.