Description of problem: Currently bitrot using 120 sec wait time for object to signing after releasing all the fops. This waiting time value should be tunable for QA testing. Version-Release number of selected component (if applicable): Mainline.
REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object signing waiting time value for bitrot) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object signing waiting time value for bitrot) posted (#4) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object signing waiting time value for bitrot) posted (#5) for review on master by Gaurav Kumar Garg (ggarg)
REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object signing waiting time value for bitrot) posted (#7) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object signing waiting time value for bitrot) posted (#8) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/11105 (features/bitrot: tuanble object signing waiting time value for bitrot) posted (#9) for review on master by Gaurav Kumar Garg (ggarg)
COMMIT: http://review.gluster.org/11105 committed in master by Venky Shankar (vshankar) ------ commit 554fa0c1315d0b4b78ba35a2d332d7ac0fd07d48 Author: Gaurav Kumar Garg <ggarg> Date: Fri Jun 5 13:58:28 2015 +0530 features/bitrot: tuanble object signing waiting time value for bitrot Currently bitrot using 120 second waiting time for object to be signed after all fop's released. This signing waiting time value should be tunable. Command for changing the signing waiting time will be #gluster volume bitrot <VOLNAME> signing-time <waiting time value in second> Change-Id: I89f3121564c1bbd0825f60aae6147413a2fbd798 BUG: 1228680 Signed-off-by: Gaurav Kumar Garg <ggarg> Signed-off-by: Venky Shankar <vshankar> Reviewed-on: http://review.gluster.org/11105
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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