Re: Framework still active after calling driver.stop

This is because stop() is asynchronously processed. A message is sent to the scheduler process and it will eventually send the message to the master. This is why you've noticed that sleeping helps to ensure that this occurs. There is no scheduler driver specific issue for this, but the executor

Framework still active after calling driver.stop

Hi, We have a production pipeline running a series of jobs, with each job creating a custom mesos framework to execute all tasks related to that job. Both scheduler and executor are written using the Python mesos API. Here's a snippet (modified for brevity) of the scheduler code: class