[Bugs] [Bug 1622076] [geo-rep]: geo-rep reverse sync in FO/ FB can accidentally delete the content at original master incase of gfid conflict in 3.4.0 without explicit user rmdir

bugzilla at redhat.com bugzilla at redhat.com
Mon Aug 27 03:46:36 UTC 2018


Worker Ant <bugzilla-bot at gluster.org> changed:

           What    |Removed                     |Added
             Status|POST                        |MODIFIED

--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/20986 committed in master by "Aravinda VK"
<avishwan at redhat.com> with a commit message- geo-rep: Make automatic gfid
conflict resolution optional

Autmatic gfid conflict resolution needs to be disabled
during failover/failback as it might lead to data loss
in the following scenario.

1. Master went down without syncing directory "dir1" to slave.
2. When slave is failed over to master, if a new file
   is written inside "dir1", creating dir1 again if not
   present, "dir1" ends up with different gfid on original
3. When original master is up and failed back, due to
   automatic gfid conflict resolution, "dir1" present in
   original master is deleted losing all files and only
   new file created on original slave is restored.

Hence during failover/failback, automatic gfid conflict
resolution should be disabled. So in these cases, appropriate
decision is taken.

fixes: bz#1622076
Signed-off-by: Kotresh HR <khiremat at redhat.com>
Change-Id: I433616f5d3e13d4b6eb675475bd554ca34928573

You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=vGDoiqQK0V&a=cc_unsubscribe

More information about the Bugs mailing list