[Bugs] [Bug 1267185] New: geo-replication: Fix races while handling rebalanced data in Tiering volume

bugzilla at redhat.com bugzilla at redhat.com
Tue Sep 29 09:20:40 UTC 2015


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

            Bug ID: 1267185
           Summary: geo-replication: Fix races while handling rebalanced
                    data in Tiering volume
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs-geo-replication
          Assignee: rhs-bugs at redhat.com
          Reporter: sarumuga at redhat.com
        QA Contact: storage-qa-internal at redhat.com
                CC: bugs at gluster.org, chrisw at redhat.com, csaba at redhat.com,
                    gluster-bugs at redhat.com, nlevinki at redhat.com
        Depends On: 1266875



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

Description of problem:

Race conditions can occur while processing changelogs(by geo-replication) in
Tiering based volume, where rebalanace can cause frequent movement of files
between hot and cold tiers.

Also, rebalance operations are internal operations which needs to be avoided.
(Deletion of the file and Creation of the file while carrying out rebalance).

Version-Release number of selected component (if applicable):


How reproducible:

Following is one such example:

==================================
Brick1             Brick2
==================================
Create file        (file moved due to rebalance).
            Data file
            Delete file
==================================

If Brick2 changelogs processed first followed by Brick1, file may be created.
But, we expect the file to be deleted (as per the last operation)

Steps to Reproduce:
1.
2.
3.

Actual results:
Files are not synced properly.

Expected results:
Files are synced as expected.

Additional info:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1266875
[Bug 1266875] geo-replication: Fix races while handling rebalanced data in
Tiering volume
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=fzWE4Moxm9&a=cc_unsubscribe


More information about the Bugs mailing list