Description of problem: feedback at https://review.gluster.org/#/c/18103/1//COMMIT_MSG@15 : AFR marks the arbiter brick as 'non readable', so any read-based FOP won't be sent on it.(See: http://review.gluster.org/13539). So I don't think this change is really needed. After 13539, even arbiter_readv() won't be hit as well. It might be a good idea to have this defensive fix (unwind the FOP with failure) in the rogue case AFR does wind the read fop to arbiter. Expected results: No change in behaviour, AFR should not call the FOPs from the arbiter xlator in any case.
REVIEW: https://review.gluster.org/18103 (arbiter: return ENOTCONN for 'non readable' FOPs) posted (#2) for review on master by Niels de Vos (ndevos)
REVIEW: https://review.gluster.org/18103 (arbiter: return ENOTCONN for 'non readable' FOPs) posted (#3) for review on master by Ravishankar N (ravishankar)
REVIEW: https://review.gluster.org/18103 (arbiter: return ENOTCONN for 'non readable' FOPs) posted (#4) for review on master by Ravishankar N (ravishankar)
REVIEW: https://review.gluster.org/18103 (arbiter: return ENOSYS for 'non readable' FOPs) posted (#5) for review on master by Niels de Vos (ndevos)
COMMIT: https://review.gluster.org/18103 committed in master by Ravishankar N (ravishankar) ------ commit b1352d0974328b367afa7360e9523585efb7178d Author: Niels de Vos <ndevos> Date: Wed Aug 23 18:18:24 2017 +0200 arbiter: return ENOSYS for 'non readable' FOPs AFR marks the arbiter as 'non readable'. This has been introduced with commit 8ab87137 (afr: do not set arbiter as a readable subvol in inode context). arbiter_readv() should not get called anymore, so it could be removed. However, it is a good defensive approach to have all the inode read FOPs that can not be handled by the arbiter to return ENOSYS. Change-Id: I6ea41680832859bd6790dc8d7440ee98d38205fc BUG: 1484722 Signed-off-by: Niels de Vos <ndevos> Signed-off-by: Ravishankar N <ravishankar> Reviewed-on: https://review.gluster.org/18103 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.13.0, please open a new bug report. glusterfs-3.13.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-December/000087.html [2] https://www.gluster.org/pipermail/gluster-users/