This is an umbrella bug to track the ongoing effort of improving client I/O latencies observed when objects are signed.
REVIEW: http://review.gluster.org/11461 (features/bitrot: move inode state just at the last moment) posted (#2) for review on master by Venky Shankar (email@example.com)
REVIEW: http://review.gluster.org/11461 (features/bitrot: move inode state just at the last moment) posted (#3) for review on master by Venky Shankar (firstname.lastname@example.org)
Not moving bug state as there would be multiple patches (first improvement posted) to improve client I/O performance.
COMMIT: http://review.gluster.org/11461 committed in master by Raghavendra Bhat (email@example.com)
Author: Venky Shankar <firstname.lastname@example.org>
Date: Tue Jun 30 13:10:46 2015 +0530
features/bitrot: move inode state just at the last moment
Which was done at half the set expiry time resulting in actual
IOs incrementing the object version. Now this is done just at
the last moment with re-notification now cut-shorting into
checksum calculation without waiting in the timer-wheel.
Signed-off-by: Venky Shankar <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Raghavendra Bhat <firstname.lastname@example.org>
Let's keep this ASSIGNED as there would be other enhancements too (throttle signer, etc.)
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.