[Gluster-devel] [Gluster-Maintainers] Client Server incompatibility with Gluster 4.0

Vijay Bellur vbellur at redhat.com
Thu Oct 12 03:29:40 UTC 2017

On Wed, Oct 11, 2017 at 5:06 AM, Amar Tumballi <atumball at redhat.com> wrote:

> Was (Re: [Gluster-devel] Proposed Protocol changes for 4.0: Need feedback.)
> All,
> While we are at making all the below tasks' color coding to GREEN, it
> would make sense to discuss 1 main thing.
> With 4.0, we will anyways say 3.y series server nodes are not going to be
> compatible with 4.x servers, is it the same case with clients?
> If yes, I am considering some changes to the current way RPC conversion is
> handled in protocol layer, and make it simpler a bit.
> If no, then I have to add lot of 'if..else' in existing code or extra code
> wherever applicable, now, to make sure we handle the compatibility better.
> My personal opinion is, talk about incompatibility now, and plan to have
> smooth sail even when 5.0 lands. We are anyways coming out with GD2 (which
> makes servers incompatible), and gfproxy (which makes clients missing this
> feature in older releases), and also possible cherrypicks from upstream
> fuse project to utilize more features from there, so for the user, there
> are lot of reason to upgrade the clients.

Since we are bumping the major release number, I think it would be
acceptable to have 3.x clients being not compatible with 4.x servers and
vice-versa. We should ensure that accesses from incompatible clients are
handled gracefully by both servers and clients.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20171011/7443f793/attachment.html>

More information about the Gluster-devel mailing list