[Bugs] [Bug 1672314] New: thin-arbiter: Check with thin-arbiter file before marking new entry change log

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1672314

            Bug ID: 1672314
           Summary: thin-arbiter: Check with  thin-arbiter file before
                    marking new entry change log
           Product: GlusterFS
           Version: 5
            Status: NEW
         Component: replicate
          Assignee: bugs at gluster.org
          Reporter: aspandey at redhat.com
                CC: bugs at gluster.org
        Depends On: 1662264
  Target Milestone: ---
    Classification: Community



+++ This bug was initially created as a clone of Bug #1662264 +++

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:

--- Additional comment from Worker Ant on 2018-12-27 09:19:25 UTC ---

REVIEW: https://review.gluster.org/21933 (cluster/thin-arbiter: Consider
thin-arbiter before marking new entry changelog) posted (#1) for review on
master by Ashish Pandey

--- Additional comment from Worker Ant on 2019-02-01 05:45:32 UTC ---

REVIEW: https://review.gluster.org/21933 (cluster/thin-arbiter: Consider
thin-arbiter before marking new entry changelog) merged (#6) on master by Amar
Tumballi


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1662264
[Bug 1662264] thin-arbiter: Check with  thin-arbiter file before marking new
entry change log
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.