Mesos 0.16.0 Released

We recently released Mesos v0.16.0 on our downloads page. It includes major refactoring work of the leading master election and detection process. This improves the reliability and flexibility of running multiple masters in your cluster, which provides Mesos with high availability.

In high availability mode, if a leading master machine fails, Mesos holds elections to determine a new leader. Slave machines and schedulers detect the new leading master and connect to it, without disrupting services running on Mesos. Leader election implementation details, including how it works with Zookeeper, are detailed in the high availablity documentation.

What’s Changed

Aside from the refactoring, v0.16.0 includes fixes for bugs which caused incorrect termination of Mesos masters and slaves:

Fixed ZooKeeper related bugs which terminated Mesos processes instead of automatically retrying them: MESOS-463, MESOS-465, MESOS-814.
Non-leading Master now stays up after ZooKeeper session expiration or after it is partitioned from ZooKeeper.
Slave no longer attempts to recover checkpointed data after a reboot: MESOS-844.

Click to read the full release notes.

Upgrading

To upgrade a live cluster, please refer to the Upgrades document.

Getting Involved

We encourage you to try out this release, and let us know what you think on the user mailing list. You can also get in touch with us via @ApacheMesos or via mailing lists and IRC.