mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yan Xu (JIRA)" <>
Subject [jira] [Created] (MESOS-6574) Define Mesos behavior with incompatible components
Date Thu, 10 Nov 2016 20:05:58 GMT
Yan Xu created MESOS-6574:

             Summary: Define Mesos behavior with incompatible components
                 Key: MESOS-6574
             Project: Mesos
          Issue Type: Task
            Reporter: Yan Xu

As per the versioning guide

users should be able to upgrade (as long as they are not depending on deprecated / removed
features) Mesos master or agent from a stable release version N directly to another stable
release version M without having to go through intermediate release versions.

Sometimes compatibility breaks not because users have chosen to use deprecated / removed features
but rather due to the change of communication protocol between Master and the agents. One
motivating example is MESOS-6483.

This means when upgrading Mesos from version N to M despite the operators' best effort, Mesos
components (mainly master/agent) of different versions may just be incompatible. 

We should
1) Clarify the window of compatibility between master/agents.
2) Define (and implement) Mesos behavior when one component interfaces with another of an
incompatible version.

For 2), it's necessary because even if you can require operators to not run incompatible versions
of master/agents, in practice there are always going to be stranglers that fall behind upgrade
schedule or inadvertently come back to life from hibernation. When this happens, Mesos (at
least the master) shouldn't crash, but rather be defensive and reject the the call/event and
log a warning.

This message was sent by Atlassian JIRA

View raw message