Description of problem: Slave ENTRY operation failures cannot be traced due to lack of information on failing operations Version-Release number of selected component (if applicable): mainline How reproducible: CREATE Mount file-system on slave and create a file Mount file-system on master the create the same file Operation should fail on slave and there's no trace left behind about the failure Similarly, RENAME and UNLINK operations also need to be tracked for failures on slave Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/10048 (add logging on master for ENTRY operation errors from slave) posted (#1) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/10048 (geo-rep: add logging on master for ENTRY operation errors from slave) posted (#2) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/10048 (add logging on master for ENTRY operation errors from slave) posted (#3) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/10048 (geo-rep: add logging on master for ENTRY operation errors from slave) posted (#4) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/10048 (features/geo-rep: add logging on master for ENTRY operation errors from slave) posted (#5) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/10048 (features/geo-rep: add logging on master for ENTRY operation errors from slave) posted (#6) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/10048 (geo-rep: add logging on master for ENTRY operation errors from slave) posted (#7) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/10048 (geo-rep: add logging on master for ENTRY operation errors from slave) posted (#8) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/10048 (geo-rep: add logging on master for ENTRY operation errors from slave) posted (#9) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/10048 (geo-rep: add logging on master for ENTRY operation errors from slave) posted (#10) for review on master by Milind Changire (mchangir)
REVIEW: http://review.gluster.org/10048 (geo-rep: log ENTRY failures from slave on master) posted (#11) for review on master by Milind Changire (mchangir)
COMMIT: http://review.gluster.org/10048 committed in master by Vijay Bellur (vbellur) ------ commit 70a729e9751e45e266f7462443dcf2b6be3cecbe Author: Milind Changire <mchangir> Date: Mon Mar 30 16:53:05 2015 +0530 geo-rep: log ENTRY failures from slave on master ENTRY operations failures on slave left no trace for debugging purposes. This patch captures such failures on slave cluster and forwards them to the master and logs them. Failures of specific interest are the ones which return code EEXIST on the failing operations. Change-Id: Iecab876f16593c746d53f4b7ec2e0783367856bb BUG: 1207115 Signed-off-by: Milind Changire <mchangir> Reviewed-on: http://review.gluster.org/10048 Reviewed-by: Aravinda VK <avishwan> Tested-by: NetBSD Build System Tested-by: Gluster Build System <jenkins.com>
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.7.0, please open a new bug report.
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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user