[Bugs] [Bug 1662264] New: thin-arbiter: Check with thin-arbiter file before marking new entry change log
bugzilla at redhat.com
bugzilla at redhat.com
Thu Dec 27 09:08:23 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1662264
Bug ID: 1662264
Summary: thin-arbiter: Check with thin-arbiter file before
marking new entry change log
Product: GlusterFS
Version: mainline
Status: NEW
Component: replicate
Assignee: bugs at gluster.org
Reporter: aspandey at redhat.com
CC: bugs at gluster.org
Target Milestone: ---
Classification: Community
Description of problem:
In case of creating an entry, if a fop fails on any one of the data bricks,
we mark the changelog on that entry on the brick which was successful.
For thin arbiter volume before marking this changelog, we should check if the
brick on which fop succeeded was the good brick or not. If the bricks was bad
according to thin-arbiter file information, we should just continue with postop
changelog process. If the brick was good, we should mark the new entry
changelog and continuew with postop changelog.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list