[PATCH] Do not allow different versions of ctdb in a cluster
amitay at gmail.com
Wed May 24 01:41:51 UTC 2017
Clearly that falls under "you known what you are doing!" :-)
Yes, that's the idea. The tunable is mainly to cater for rolling upgrades.
On Wed, May 24, 2017 at 5:07 AM, Christopher R. Hertel via samba-technical <
samba-technical at lists.samba.org> wrote:
> What about rolling upgrades? When the goal is to upgrade a running cluster
> to the latest and greatest, will we need to set AllowMixedVersions first
> then perform the upgrade? Will that even work?
> Chris -)-----
> On 05/22/2017 11:40 PM, Amitay Isaacs via samba-technical wrote:
> > Hi,
> > Till now there has never been a check to ensure that compatible ctdb
> > versions are running in a cluster. We allowed different versions of ctdb
> > in a cluster. This patch set adds a check to ensure that a cluster has
> > compatible versions of ctdb.
> > As a general rule, ctdb with same major and minor versions will be
> > compatible.
> > However allow the flexibility of mixing versions if you know what you are
> > doing via new tunable AllowMixedVersions.
> > Please review and push.
> > These patches are dependent on the set of patches posted previously
> > (simplify generation of version header files in ctdb build).
> > Amitay.
More information about the samba-technical