[Bugs] [Bug 1708121] New: Geo-rep: Data inconsistency while syncing heavy renames with constant destination name

[bugzilla at redhat.com]

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

            Bug ID: 1708121
           Summary: Geo-rep: Data inconsistency while syncing heavy
                    renames with constant destination name
           Product: Red Hat Gluster Storage
           Version: rhgs-3.5
            Status: NEW
         Component: geo-replication
          Assignee: sunkumar at redhat.com
          Reporter: khiremat at redhat.com
        QA Contact: rhinduja at redhat.com
                CC: avishwan at redhat.com, bugs at gluster.org,
                    csaba at redhat.com, khiremat at redhat.com,
                    rhs-bugs at redhat.com, sankarshan at redhat.com,
                    storage-qa-internal at redhat.com, sunkumar at redhat.com
        Depends On: 1694820
  Target Milestone: ---
    Classification: Red Hat



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

Description of problem:

This problem only exists in heavy RENAME workload where parallel rename are
frequent or doing RENAME with existing destination.


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


How reproducible:
Always

Steps to Reproduce:
1. Run frequent RENAME on master mount and check for sync in slave.

Ex - while true; do uuid="`uuidgen`"; echo "some data" > "test$uuid"; mv
"test$uuid" "test" -f; done 

Actual results:

Does not syncs renames properly and creates multiples files in slave.

Expected results:
Should sync renames.

--- Additional comment from Worker Ant on 2019-04-01 19:10:45 UTC ---

REVIEW: https://review.gluster.org/22474 (geo-rep: fix rename with existing
gfid) posted (#1) for review on master by Sunny Kumar

--- Additional comment from Worker Ant on 2019-04-07 05:23:33 UTC ---

REVIEW: https://review.gluster.org/22519 (geo-rep: Fix rename with existing
destination with same gfid) posted (#1) for review on master by Kotresh HR

--- Additional comment from Worker Ant on 2019-04-26 07:15:41 UTC ---

REVIEW: https://review.gluster.org/22519 (geo-rep: Fix rename with existing
destination with same gfid) merged (#7) on master by Amar Tumballi


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1694820
[Bug 1694820] Geo-rep: Data inconsistency while syncing heavy renames with
constant destination name
-- 
You are receiving this mail because:
You are on the CC list for the bug.