[MESOS-1534] Scheduler process is not explicitly terminated in the destructor of MesosSchedulerDriver.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.19.1
• Target Version/s: 0.19.1, 0.20.0
• Sprint: Q2 Sprint 4
• Assignee: Vinod Kone
• Reporter: Vinod Kone
• Created: 24/Jun/14 04:50
• Updated: 14/Jul/14 21:00
• Resolved: 24/Jun/14 18:24

Description

When a Mesos test fails due to an assertion error driver.stop() is not called but ~MesosSchedulerDriver() might be called (if it's on the stack). The destructor will block on the scheduler process termination which never happens because driver.stop() is not called.

Issue Links

• duplicates: MESOS-445 Scheduler driver destructor waits forever