[Bugs] [Bug 1239044] [geo-rep]: killing brick from replica pair makes geo-rep session faulty with Traceback "ChangelogException"

[bugzilla at redhat.com]

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



--- Comment #4 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11524 committed in master by Venky Shankar
(vshankar at redhat.com) 
------
commit 62c2e7f8b9211ba149368d26f772f175fe51b43b
Author: Kotresh HR <khiremat at redhat.com>
Date:   Fri Jul 3 16:32:56 2015 +0530

    geo-rep: Fix history failure

    Both ACTIVE and PASSIVE workers register to changelog
    at almost same time. When PASSIVE worker becomes ACTIVE,
    the start and end time would be current stime and register_time
    repectively for history API. Hence register_time would be less
    then stime for which history obviously fails. But it will
    be successful for the next restart as new register_time > stime.

    Fix is to pass current time as the end time to history call
    instead of the register_time.

    Also improvised the logging for ACTIVE/PASSIVE switching.

    Change-Id: Idc08b4b55c7a4c575ba44918a98389164ccbee8f
    BUG: 1239044
    Signed-off-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-on: http://review.gluster.org/11524
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Aravinda VK <avishwan at redhat.com>
    Reviewed-by: Venky Shankar <vshankar 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=h12tw8Isjt&a=cc_unsubscribe