[DRBD-user] Running Different Versions of drbd / kmod-drbd on different nodes

[Eric Robinson]

Thanks, Roland.

> -----Original Message-----
> From: drbd-user-bounces at lists.linbit.com <drbd-user-
> bounces at lists.linbit.com> On Behalf Of Roland Kammerer
> Sent: Wednesday, May 25, 2022 1:58 AM
> To: drbd-user at lists.linbit.com
> Subject: Re: [DRBD-user] Running Different Versions of drbd / kmod-drbd on
> different nodes
>
> On Tue, May 24, 2022 at 04:43:18PM +0000, Eric Robinson wrote:
> > If a cluster has 4 data nodes, and they are deployed in such a way
> > that Nodes 1 & 2 replicate only to each other, and Nodes 3 & 4
> > replicate only to each other, is it okay to run Nodes 1 & 2 on a
> > different version of drbd and kmod-drbd than nodes 3 & 4?
>
> Should be fine in general. I mean what if you upgrade nodes, and you
> upgrade 1 and then reconnect, then you also have 2 different versions.
> And that is a of course a supported upgrade scenario.  And in your case they
> don't even talk to each other. Anyways, when a resource connects to a peer
> there is a handshake and there min and max protocol versions get
> exchanged and as long as they have some common ground the connection
> get's established, otherwise aborted. Fun fact: there is current work that
> latest DRBD9 can even talk to 8.4 again.
>
> Regards, rck
> _______________________________________________
> Star us on GITHUB: https://github.com/LINBIT drbd-user mailing list drbd-
> user at lists.linbit.com https://lists.linbit.com/mailman/listinfo/drbd-user
Disclaimer : This email and any files transmitted with it are confidential and intended solely for intended recipients. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physician Select Management. Warning: Although Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.