[Bugs] [Bug 1290655] New: Sharding: Remove dependency on performance.strict-write-ordering
bugzilla at redhat.com
bugzilla at redhat.com
Fri Dec 11 04:45:36 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1290655
Bug ID: 1290655
Summary: Sharding: Remove dependency on
performance.strict-write-ordering
Product: GlusterFS
Version: 3.7.6
Component: sharding
Keywords: Triaged
Assignee: bugs at gluster.org
Reporter: kdhananj at redhat.com
QA Contact: bugs at gluster.org
CC: bugs at gluster.org
Depends On: 1289840
+++ This bug was initially created as a clone of Bug #1289840 +++
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):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--- Additional comment from Vijay Bellur on 2015-12-09 01:38:36 EST ---
REVIEW: http://review.gluster.org/12915 (tests, shard: Remove dependency on
strict-write-ordering) posted (#1) for review on master by Krutika Dhananjay
(kdhananj at redhat.com)
--- Additional comment from Vijay Bellur on 2015-12-10 23:40:53 EST ---
COMMIT: http://review.gluster.org/12915 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com)
------
commit 3a01c1b36724ad4c9148540b56a26b3c1799c583
Author: Krutika Dhananjay <kdhananj at redhat.com>
Date: Tue Dec 8 14:31:30 2015 +0530
tests, shard: Remove dependency on strict-write-ordering
Change-Id: I00171a77bdefb1c2e7e4610cb0ade5679bdb761f
BUG: 1289840
Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
Reviewed-on: http://review.gluster.org/12915
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1289840
[Bug 1289840] Sharding: Remove dependency on
performance.strict-write-ordering
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list