Bug 1595916 - geo-replication fails with xsync
Summary: geo-replication fails with xsync
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Shwetha K Acharya
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-27 18:47 UTC by Chad Cropper
Modified: 2020-01-31 12:19 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-01-31 12:19:26 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
geo_repl.log (3.90 KB, text/plain)
2018-06-27 18:47 UTC, Chad Cropper
no flags Details

Description Chad Cropper 2018-06-27 18:47:38 UTC
Created attachment 1455109 [details]
geo_repl.log

Description of problem:
geo-replication status says Active Hybrid Crawl, but the logs say the connection to peer is broken. Recreating geo-repl keeping data on slave. Previous geo-repl was set with ignore_deletes=1

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

How reproducible:
Easy

Steps to Reproduce:
1. gluster volume geo-replication fit_outbox usfit-gfs1.global.internal::wau_inbox stop
2. gluster volume geo-replication fit_outbox usfit-gfs1.global.internal::wau_inbox delete reset-sync-time
3. gluster system:: execute gsec_create
4. gluster volume geo-replication fit_outbox usfit-gfs1.global.internal::wau_inbox create push-pem force
5. gluster volume geo-replication fit_outbox usfit-gfs1.global.internal::wau_inbox start

Actual results:
See attached log file

Expected results:
geo-repl sync success

Additional info:

Comment 1 Shyamsundar 2018-10-23 14:53:53 UTC
Release 3.12 has been EOLd and this bug was still found to be in the NEW state, hence moving the version to mainline, to triage the same and take appropriate actions.

Comment 2 Sunny Kumar 2019-07-04 09:37:12 UTC
When we delete geo-rep session then we do not disable changelog.

So one workaround will be disabling changelog after session deletion and then create fresh session.

gluster volume set <volname> changelog off.


@Shwetha please verify the workaround.

Comment 3 Shwetha K Acharya 2019-07-04 09:54:37 UTC
Yes @Sunny. This workaround manages to give expected result.

Comment 4 Sunny Kumar 2020-01-31 12:19:26 UTC
Closing this bug as workaround for this issue is provided in comment#2 and verified by Shwetha(see comment#3).


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