[
https://issues.apache.org/jira/browse/MESOS-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-986:
----------------------------------
Description:
Message versioning in Mesos provides a number of benefits:
(1) Prevent incompatible version combinations. For example, we want to reject
slaves that are > 1 version behind the master.
(2) The biggest win is providing the ability to determine behavior based on the
cross-component versioning. For example, in MESOS-1668 we wanted the master to
send a different ping message based on the version of the slave. In MESOS-1696,
we wanted to perform reconciliation in the master based on the version of the
slave. In both cases, when we don't have the version, we have to either rely on
hacks/tricks, or add additional phases.
was:
Message versioning in Mesos provides a number of benefits:
# Prevent incompatible version combinations. For example, we want to reject
slaves that are > 1 version behind the master.
# The biggest win is providing the ability to determine behavior based on the
cross-component versioning. For example, in MESOS-1668 we wanted the master to
send a different ping message based on the version of the slave. In MESOS-1696,
we wanted to perform reconciliation in the master based on the version of the
slave. In both cases, when we don't have the version, we have to either rely on
hacks/tricks, or add additional phases.
> Add versioning to messages.
> ---------------------------
>
> Key: MESOS-986
> URL: https://issues.apache.org/jira/browse/MESOS-986
> Project: Mesos
> Issue Type: Improvement
> Reporter: Benjamin Mahler
>
> Message versioning in Mesos provides a number of benefits:
> (1) Prevent incompatible version combinations. For example, we want to reject
> slaves that are > 1 version behind the master.
> (2) The biggest win is providing the ability to determine behavior based on
> the cross-component versioning. For example, in MESOS-1668 we wanted the
> master to send a different ping message based on the version of the slave. In
> MESOS-1696, we wanted to perform reconciliation in the master based on the
> version of the slave. In both cases, when we don't have the version, we have
> to either rely on hacks/tricks, or add additional phases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
