[Bugs] [Bug 1159195] dist-geo-rep: geo-rep status in one of rebooted node remains at "Stable(paused)" after session is resumed.

[bugzilla at redhat.com]

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



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9021 committed in release-3.6 by Venky
Shankar (vshankar at redhat.com) 
------
commit beedf68266f19ac77b77f2ec5f9533f3e63c159f
Author: Kotresh HR <khiremat at redhat.com>
Date:   Fri Oct 3 17:35:47 2014 +0530

    glusterd/geo-rep: Fix race in updating status file

    When geo-rep is in paused state and a node in a cluster
    is rebooted, the geo-rep status goes to "faulty (Paused)"
    and no worker processes are started on that node yet. In
    this state, when geo-rep is resumed, there is a race in
    updating status file between glusterd and gsyncd itself
    as geo-rep is resumed first and then status is updated.
    glusterd tries to update to previous state and gsyncd
    tries to update it to "Initializing...(Paused)" on
    restart as it was paused previously. If gsyncd on restart
    wins, the state is always paused but the process is not
    acutally paused. So the solution is glusterd to update
    the status file and then resume.

    BUG: 1159195
    Change-Id: I4c06f42226db98f5a3c49b90f31ecf6cf2b6d0cb
    Reviewed-on: http://review.gluster.org/8911
    Signed-off-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-on: http://review.gluster.org/9021
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Venky Shankar <vshankar at redhat.com>
    Tested-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=MUWb6aCAN3&a=cc_unsubscribe