Bug 1224906

Summary:	[geo-rep]: Note section in document is required for ignore_deletes true config option where it might delete a file
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Rahul Hinduja <rhinduja>
Component:	geo-replication	Assignee:	Shwetha K Acharya <sacharya>
Status:	CLOSED ERRATA	QA Contact:	Vinayak Papnoi <vpapnoi>
Severity:	low	Docs Contact:
Priority:	low
Version:	rhgs-3.1	CC:	asakthiv, chrisw, csaba, nlevinki, puebele, sacharya, sheggodu, ssivakum, vpapnoi
Target Milestone:	---	Keywords:	EasyFix, ZStream
Target Release:	RHGS 3.5.z Batch Update 4
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-6.0-53	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1708603 (view as bug list)		Environment:
Last Closed:	2021-04-29 07:20:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1922115
Bug Blocks:	1223636, 1708603

Description Rahul Hinduja 2015-05-26 07:44:52 UTC

Description of problem:
=======================

By default the ignore_deletes option is set to false. At this time, the deletes are picked up by changelog crawl and is sync to the slave. If you set the ignore_deletes option is set explicitly to true. The deletes from master are not synced to slave. This is expected. 

But there exist a window of 15 sec, where the deletes are picked up by history crawl when the ignore_delete is set to true. And it eventually deletes the file from slave which was not supposed to be deleted as it was deleted on master when ignore_deletes was set to true. This is working as per design. A note section is definitely needed.

For reference:
==============

File ifcfg-lo was deleted when ignore_deletes were set to true but is picked up by history as:

[root@georep1 .processed]# cat CHANGELOG.1432625003
E becf2ec0-c94e-4831-aa60-6b01b8114966 UNLINK 1acd9346-4794-42fc-a7e6-7f95c8a4eb26%2Fifcfg-lo
[root@georep1 .processed]# pwd
/var/lib/misc/glusterfsd/master/ssh%3A%2F%2Froot%4010.70.46.154%3Agluster%3A%2F%2F127.0.0.1%3Aslave/c19b89ac45352ab8c894d210d136dd56/.history/.processed
[root@georep1 .processed]# 



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

glusterfs-3.7.0-2.el6rhs.x86_64


How reproducible:
=================
1/1

Comment 4 Aravinda VK 2018-02-06 08:08:30 UTC

Geo-replication support added to Glusterd2 project, which will be available with Gluster upstream 4.0 and 4.1 releases. 

Most of the issues already fixed with issue https://github.com/gluster/glusterd2/issues/271 and remaining fixes are noted in issue https://github.com/gluster/glusterd2/issues/557

We can close these issues since we are not planning any fixes for 3.x series.

Comment 6 Aravinda VK 2018-11-19 07:44:29 UTC

Fix is required in Geo-rep CLI to print warning when ignore-delete option is set.

Comment 7 Shwetha K Acharya 2019-05-10 10:45:34 UTC

Posted upstream: https://review.gluster.org/22702

Comment 28 Amrita 2021-02-22 09:32:35 UTC

Ok noted Shwetha

Comment 30 errata-xmlrpc 2021-04-29 07:20:37 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (glusterfs bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:1462