Bug 1694820 - 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: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sunny Kumar
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1708121
TreeView+ depends on / blocked
 
Reported: 2019-04-01 19:01 UTC by Sunny Kumar
Modified: 2019-06-18 07:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1708121 (view as bug list)
Environment:
Last Closed: 2019-04-26 07:15:41 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 22474 0 None Abandoned geo-rep: fix rename with existing gfid 2019-04-28 07:09:57 UTC
Gluster.org Gerrit 22519 0 None Merged geo-rep: Fix rename with existing destination with same gfid 2019-04-26 07:15:40 UTC

Description Sunny Kumar 2019-04-01 19:01:58 UTC
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-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

Comment 2 Worker Ant 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

Comment 3 Worker Ant 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


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