[Gluster-Maintainers] [Gluster-devel] Proposed Protocol changes for 4.0: Need feedback.

Raghavendra G raghavendra at gluster.com
Fri Sep 1 09:02:43 UTC 2017

If we plan to fix, bz [1] is another candidate that has to be targeted for

Gluster's XDR does not conform to RFC spec

Description of problem:  In an attempt to generate bindings to
Gluster's XDR with Rust I've run into a few problems.  It appears the
XDR .x spec files are using keywords that are not legal according to
the RFC spec https://tools.ietf.org/html/rfc4506.html.  This hinders
language adoption of Gluster.  If anyone would like to produce pure
language bindings this prevents them from succeeding.  Indeed I think
community adoption of Gluster would benefit from having a wider range
of XDR bindings on which to build tooling.

Some of the problems I've encountered:
1. RFC4506 doesn't define "long" as a basic type in .x files; unsigned
hyper is its 64 bit unsigned type.
2. Also unsigned char uuid[16] not defined
Possibly other problems that I haven't gotten to yet as the parser
moves through the files.

Version-Release number of selected component (if applicable):

How reproducible: Always reproducible.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1336889

On Fri, Sep 1, 2017 at 2:29 PM, Soumya Koduri <skoduri at redhat.com> wrote:

> On 08/11/2017 06:04 PM, Amar Tumballi wrote:
>> Hi All,
>> Below are the proposed protocol changes (ie, XDR changes on the wire) we
>> are thinking for Gluster 4.0.
> Poornima and I were discussing if we can include volume uuid as part of
> Handshake protocol between protocol/client and protocol/server so that
> clients do not re-connect if the volume was deleted and recreated with the
> same name, eliminating potential issues at upper layers [1].
> We haven't looked into details, but the idea is to have glusterd2 send
> volume uuid as part of GETSPEC request to clients & brick processes which
> shall be used by protocol/client & protocol/server (may be along with vol
> name as well) during HNDSK_SETVOLUME.
> Poornima/Ram,
> Please add if I missed out anything.
> Thanks,
> Soumya
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1463191
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel

Raghavendra G
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20170901/84be1a5e/attachment.html>

More information about the maintainers mailing list