Red Hat Bugzilla – Bug 1289840
Sharding: Remove dependency on performance.strict-write-ordering
Last modified: 2016-06-16 09:49:41 EDT
Description of problem:
Same as "Summary". With http://review.gluster.org/#/c/12907/, iozone runs fine even without strict-write-ordering enabled on distributed replicated volumes.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: http://review.gluster.org/12915 (tests, shard: Remove dependency on strict-write-ordering) posted (#1) for review on master by Krutika Dhananjay (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/12915 committed in master by Pranith Kumar Karampuri (email@example.com)
Author: Krutika Dhananjay <firstname.lastname@example.org>
Date: Tue Dec 8 14:31:30 2015 +0530
tests, shard: Remove dependency on strict-write-ordering
Signed-off-by: Krutika Dhananjay <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Pranith Kumar Karampuri <firstname.lastname@example.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.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.