[Bugs] [Bug 1500853] [geo-rep]: Incorrect last sync "0" during hystory crawl after upgrade/stop-start

bugzilla at redhat.com bugzilla at redhat.com
Wed Oct 11 15:19:11 UTC 2017


--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/18494 committed in release-3.12 by jiffin
tony Thottan (jthottan at redhat.com) 
commit 19cff934acb6893f12c1617e99c3131439374513
Author: Kotresh HR <khiremat at redhat.com>
Date:   Tue Oct 10 08:25:19 2017 -0400

    geo-rep: Fix passive brick's last sync time

    Passive brick's stime was not updated to the
    status file immediately after updating the brick
    root. As a result the last sync time was showing
    '0' until it finishes first crawl if passive
    worker becomes active after restart. Fix is to
    update the status file immediately after upgrading
    the brick root.

    > Change-Id: I248339497303bad20b7f5a1d42ab44a1fe6bca99
    > BUG: 1500346
    > Signed-off-by: Kotresh HR <khiremat at redhat.com>
    (cherry picked from commit f18a47ee7e6e06c9a9a8893aef7957f23a18de53)

    Change-Id: I248339497303bad20b7f5a1d42ab44a1fe6bca99
    BUG: 1500853
    Signed-off-by: Kotresh HR <khiremat at redhat.com>

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

More information about the Bugs mailing list