You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Neil Conway (JIRA)" <ji...@apache.org> on 2016/03/02 22:08:18 UTC
[jira] [Updated] (MESOS-1315) Update master to use a "strict"
registry, by default.
[ https://issues.apache.org/jira/browse/MESOS-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neil Conway updated MESOS-1315:
-------------------------------
Description:
Upgrading into a "strict" replicated log backed registry can be done smoothly in two steps:
0.18.0 -> 0.19.0: this can go to a "non-strict", replicated log backed registry, which allows the replicated state to be bootstrapped from the current state of a cluster. The state would not be used to enforce any decisions. It will be "write-only" in this sense.
0.19.0 -> 0.20.0: this can move from a "non-strict" replicated log backed registry, to a "strict" one. This completes the upgrade, at which point reconciliation would be fully supported.
was:
This is required for 0.20.0.
Upgrading into a "strict" replicated log backed registry can be done smoothly in two steps:
0.18.0 -> 0.19.0: this can go to a "non-strict", replicated log backed registry, which allows the replicated state to be bootstrapped from the current state of a cluster. The state would not be used to enforce any decisions. It will be "write-only" in this sense.
0.19.0 -> 0.20.0: this can move from a "non-strict" replicated log backed registry, to a "strict" one. This completes the upgrade, at which point reconciliation would be fully supported.
> Update master to use a "strict" registry, by default.
> -----------------------------------------------------
>
> Key: MESOS-1315
> URL: https://issues.apache.org/jira/browse/MESOS-1315
> Project: Mesos
> Issue Type: Task
> Components: master
> Reporter: Benjamin Mahler
>
> Upgrading into a "strict" replicated log backed registry can be done smoothly in two steps:
> 0.18.0 -> 0.19.0: this can go to a "non-strict", replicated log backed registry, which allows the replicated state to be bootstrapped from the current state of a cluster. The state would not be used to enforce any decisions. It will be "write-only" in this sense.
> 0.19.0 -> 0.20.0: this can move from a "non-strict" replicated log backed registry, to a "strict" one. This completes the upgrade, at which point reconciliation would be fully supported.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)