[Bugs] [Bug 1217944] New: Changelog: Changelog should be treated as discontinuous only on changelog enable/disable

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1217944

            Bug ID: 1217944
           Summary: Changelog: Changelog should be treated as
                    discontinuous only on changelog enable/disable
           Product: GlusterFS
           Version: 3.7.0
         Component: geo-replication
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    sanandpa at redhat.com
        Depends On: 1211327



+++ This bug was initially created as a clone of Bug #1211327 +++

Description of problem:
Changelog should be treated as discontinuous only on changelog enable/disable.
On brick restart scenario, the changelog can be treated as continuous based on
following rationale.

1. In plain distributed volume, if brick goes down, no I/O can
       happen onto the brick. Hence changelog is intact with data
       on disk.
2. In distributed replicate volume, if brick goes down, since
   self-heal traffic is captured in changelog. Eventually,
   I/O happened whend brick down is captured in changelog.

This will help consumers like glusterfind and geo-replication who depend
on historical changelog consumption. Especiallly glusterfind as it doesn't
have a fallback mechanism when changelog history fails.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1211327
[Bug 1211327] Changelog: Changelog should be treated as discontinuous only
on changelog enable/disable
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.