An IRC user reported being unable to connect to his volumes after upgrading from 2.3.6 to 3.3beta3. glusterd was also unable to communicate with glusterfsd when he tried to stop the volume using the cli. [2012-05-07 23:52:19.152921] E [client-handshake.c:1821:client_dump_version_cbk] 0-testlabs-project-client-1: XDR decoding failed He had not killed his bricks. Killing the bricks and restarting glusterd solved that problem. I was under the impression that the RPC was supposed to handle trans-version interfacing to prevent this problem. Worst-case, the glusterfsd instances will need to be killed during the upgrade process.
Typo: 2.3.6 should have been 3.2.6
Joe, Because of few changes which are not compatible with 3.2.x branch and 3.3.x branch, we decided when the upgrade happens from 3.2.x to 3.3.0 branch, this will be a disruptive behavior. Will mark it for documentation bug. At this point in time, it is not feasible to do code changes to support this behavior.
In "Compatibility" section of Release Notes, we have already mentioned "Release 3.3 of GlusterFS is not compatible with 2.0.x, 3.0.x, 3.1.x, and 3.2.x releases of GlusterFS".
Release 3.3 of GlusterFS is not compatible with 2.0.x, 3.0.x, 3.1.x, and 3.2.x releases of GlusterFS. It has been mentioned in the glusterfs-3.3 release notes.