Re: Python bindings are changing!

It might work to use 0.19 with a 0.20 mesos (or visa versa), but there be dragons =) Is there a deprecation cycle? How should folks be upgrading Python schedulers and executors to 0.20.0 if they are not statically bundling libmesos? Is there an upgrade order required? We will need to

Re: multi tenant setup

Sorry for the tardy reply. Spark seems to be holding on to those resources then - are you running Spark in coarse grained mode? I am not too Spark savvy, but running in fine grained mode should allocate and free resources on-demand rather than allocating a temporary static partition up front.

Disallowing completed frameworks from re-registering with the same framework id

Hi, Currently, there is a bug in Mesos, which allows a completed framework (e.g., removed by master due to being disconnected for longer than failover timeout) to re-register with the same framework id. This causes issues in the WebUI because the same framework id exists in active and terminated