On 18 Mar 2015 Niklas Nielsen of Mesosphere — the release manager of this release — gave an insightful talk on the new features in the Apache Mesos 0.22.0 release:

The four new key features introduced with 0.22.0 that Niklas talked about are:

Disk isolation —quotas that enforce disk resource usage: this is in addition to the already supported cgroups CPU shares, RAM limits, PID namespaces, network isolation, task-level perf stats. Usage: see the new isolation flag with posix/disk value.

—quotas that enforce disk resource usage: this is in addition to the already supported cgroups CPU shares, RAM limits, PID namespaces, network isolation, task-level perf stats. Usage: see the new isolation flag with posix/disk value. Compute node removal rate limiting : the Mesos master sends heartbeat signals to the compute (or: slave) nodes for health checking. Now if, for example, there’s a network partition where the Master gets disconnected from all compute nodes on re-connect that might causes issues. So far, things like Master suicide helped mitigating this undesired situation; what’s new is that there’s a rate limit (say, 1 slave per sec) for removal.

: the Mesos master sends heartbeat signals to the compute (or: slave) nodes for health checking. Now if, for example, there’s a network partition where the Master gets disconnected from all compute nodes on re-connect that might causes issues. So far, things like Master suicide helped mitigating this undesired situation; what’s new is that there’s a rate limit (say, 1 slave per sec) for removal. Task labels : it is often required to label tasks and this has been a hack so far (on the framework-level). The TaskInfo message has now been extended with a label field that allows you to use arbitrary key/value pairs and which is available throughout all state endpoints.

: it is often required to label tasks and this has been a hack so far (on the framework-level). The TaskInfo message has now been extended with a label field that allows you to use arbitrary key/value pairs and which is available throughout all state endpoints. Hooks and decorators: orthogonal to modules, hooks are sort of event callbacks across library boundaries. Three hooks have been introduced with 0.22.0, see details in MESOS-2060.

Obviously, there are tons of fixes that come with 0.22.0, as well as service discovery support, external logs, etc. — congrats to the team, awesome progress!

Concluding, I’d say: power up your engines and give the RC4 a try!