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

[bugzilla at redhat.com]

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



--- Comment #7 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10222 committed in master by Vijay Bellur
(vbellur at redhat.com) 
------
commit 275f7244ff9bfae085cfc8ee103990100e41057f
Author: Kotresh HR <khiremat at redhat.com>
Date:   Mon Apr 13 20:28:21 2015 +0530

    features/changelog: Consider only changelog on/off as changelog breakage

    Earlier, both chagelog on/off and brick restart were considered
    to be changelog breakage and treated as changelog not being
    continuous. As a result, new HTIME.TSTAMP file was created on
    both the above cases. Now the change is made such that only
    on changelog enable/disable, the changelog is considered to be
    discontinuous. New HTIME.TSTAMP file is not created on brick
    restart, the changelogs files are appended to last HTIME.TSTAMP
    file.

    Treating changelog as continuous in above scenario is important
    as changelog history API will fail otherwise. It can successfully
    get changes between start and end timestamps only when changelog
    is continuous (Changelogs in single HTIME.TSTAMP file are treated
    as continuous). Without this change, changelog history API would
    fail, and it would become necessary to fallback to other mechanisms
    like xsync FSCrawl in case geo-rep to detect changes in this time
    window. But Xsync FSCrawl would not be applicable to other
    consumers like glusterfind.

    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.

    Change-Id: I2eb66efe6ee9a9228fb1fcb38d6e7696b9559d5b
    BUG: 1211327
    Signed-off-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-on: http://review.gluster.org/10222
    Reviewed-by: Venky Shankar <vshankar at redhat.com>
    Tested-by: Venky Shankar <vshankar at redhat.com>
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System

-- 
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=G5hxeqzcTO&a=cc_unsubscribe