Bug 1709734 - Geo-rep: Data inconsistency while syncing heavy renames with constant destination name
Summary: Geo-rep: Data inconsistency while syncing heavy renames with constant destina...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-14 08:39 UTC by Kotresh HR
Modified: 2019-05-17 07:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-17 07:48:58 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22723 0 None Merged geo-rep: Fix rename with existing destination with same gfid 2019-05-17 07:48:57 UTC

Description Kotresh HR 2019-05-14 08:39:26 UTC
This bug was initially created as a copy of Bug #1694820

I am copying this bug because: 



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.

Comment 1 Worker Ant 2019-05-14 08:52:24 UTC
REVIEW: https://review.gluster.org/22723 (geo-rep: Fix rename with existing destination with same gfid) posted (#1) for review on release-6 by Kotresh HR

Comment 2 Worker Ant 2019-05-17 07:48:58 UTC
REVIEW: https://review.gluster.org/22723 (geo-rep: Fix rename with existing destination with same gfid) merged (#2) on release-6 by Amar Tumballi


Note You need to log in before you can comment on or make changes to this bug.