[MESOS-579] Refactor the Isolator to return Futures and wrap a libprocess Process.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Labels: twitter
• Assignee: Ian Downes
• Reporter: Benjamin Mahler
• Created: 18/Jul/13 21:47
• Updated: 11/Nov/13 22:45
• Resolved: 11/Nov/13 22:45

Description

Currently the Isolator interface is a libprocess Process:

class Isolator : public process::Process<Isolator>
{
...
virtual void killExecutor(
const FrameworkID& frameworkId,
const ExecutorID& executorId) = 0;
...
}

This has led to issues where we've accidentally called directly into Isolator (instead of dispatching). We should make Isolator a wrapper around a libprocess Process.

Second, the Isolator should return Futures rather than calling back into the slave. We currently have to construct the ProcessIsolator / CgroupsIsolator by passing in the Slave PID, so that they can dispatch back into the slave to notify when the executor has exited (for example). We can eliminate the need for this by returning Futures!

class Isolator
{
...
// Returns a Future that becomes ready when the executor has been killed.
// Exited contains the status and message.
virtual Future<Exited> killExecutor(
const FrameworkID& frameworkId,
const ExecutorID& executorId);

{ return dispatch(isolator, &IsolatorProcess::killExecutor, frameworkId, executorId); }

...

private:
IsolatorProcess* isolator;
}

Issue Links

• duplicates: MESOS-600 Rework Isolator abstraction