[Bugs] [Bug 1149982] 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=1149982



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/8911 committed in master by Venky Shankar
(vshankar at redhat.com) 
------
commit 3b5b5042ec2f119e3ec807829c101c421e90e2da
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.

    Change-Id: I348761a6e8c3ad2630c79833bc86587d062a8f92
    BUG: 1149982
    Signed-off-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-on: http://review.gluster.org/8911
    Reviewed-by: Aravinda VK <avishwan at redhat.com>
    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=tT1jJiZXvY&a=cc_unsubscribe