[MESOS-8083] Mesos containerizer should run isolate() sequentially.

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: containerization
• Assignee: Unassigned
• Reporter: Yan Xu
• Created: 12/Oct/17 20:57
• Updated: 12/Oct/17 22:00

Description

Currently all the isolate() calls to all isolators are done in parallel, unlike prepare() and destroy(), which are done sequentially.

The following comment was provided as justification: https://github.com/apache/mesos/blob/615f1f0bcdfab4df264f37d2ebf528da2e6aa426/src/slave/containerizer/mesos/containerizer.cpp#L1894-L1907

  // Isolate the executor with each isolator.
  // NOTE: This is done is parallel and is not sequenced like prepare
  // or destroy because we assume there are no dependencies in
  // isolation.

However this is not strictly true, especially it's uncertain for isolator modules. To be safe we should just handle it consistently with other isolator calls and make it sequential.

Issue Links

• is related to: MESOS-7643 The order of isolators provided in '--isolation' flag is not preserved and instead sorted alphabetically