This is a bugfix release. The Release Notes for 3.5.0, 3.5.1, 3.5.2, 3.5.3 and 3.5.4 contain a listing of all the new features that were added and bugs fixed in the GlusterFS 3.5 stable release.
Bugs Fixed:
- 1166862: rmtab file is a bottleneck when lot of clients are accessing a volume through NFS
- 1217432: DHT:Quota:- brick process crashed after deleting .glusterfs from backend
- 1217433: glusterfsd crashed after directory was removed from the mount point, while self-heal and rebalance were running on the volume
- 1231641: cli crashes when listing quota limits with xml output
Known Issues:
- The following configuration changes are necessary for 'qemu' and 'samba vfs plugin' integration with libgfapi to work seamlessly:
gluster volume set <volname> server.allow-insecure on- restarting the volume is necessary
gluster volume stop <volname>
gluster volume start <volname> - Edit
/etc/glusterfs/glusterd.volto contain this line:
option rpc-auth-allow-insecure on - restarting glusterd is necessary
service glusterd restart
- For Block Device translator based volumes open-behind translator at the client side needs to be disabled.
gluster volume set <volname> performance.open-behind disabled - libgfapi clients calling
glfs_finibefore a successfulglfs_initwill cause the client to hang as reported here. The workaround is NOT to callglfs_finifor error cases encountered before a successfulglfs_init. This is being tracked in Bug 1134050 for glusterfs-3.5 and Bug 1093594 for mainline.
- If the
/var/run/glusterdirectory does not exist enabling quota will likely fail (Bug 1117888).