On Sat, Oct 4, 2014 at 1:19 PM, Colleen Lee <[email protected]> wrote:
> This normally occurs as expected, but after some time running multiple > jobs, there will be approximately a 30-minute delay between the call to > driver.run() and the registered() method being called (based on logs). > > This seems weird. Can you show us the logs? > Another thing we've noticed is that the number of threads used by the > process increases as more jobs are run. Does calling driver.stop() > terminate any threads launched for calling the native Mesos code through > JNI? Or are additional steps required? > > The ZooKeeper thread is not terminated on driver.stop() (it's a bug) but when the driver object is destructed. > One more possible weirdness -- would anything odd happen if driver.stop() > is called more than once for a particular driver? > Shouldn't be a problem.
