[Bugs] [Bug 1152890] Peer probe during rebalance causing "Peer rejected" state for an existing node in trusted cluster

[bugzilla at redhat.com]

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



--- Comment #4 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/8932 committed in master by Kaushal M
(kaushal at redhat.com) 
------
commit 8df26e838c40f15bb2b26131d1533da339f5be3e
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Wed Oct 15 12:56:48 2014 +0530

    glusterd: op state machine shouldn't use global peer list

    Problem : op state machine was relying on the global peer list while
sending
    lock/stage/unlock commit rpc requests to the peers in the cluster. Trusting
on
    global peer list structure is dangerous as this structure gets modified if
any
    peer modification command is attempted in the cluster when there is a
ongoing
    transaction going through the state machine. An ideal usecase of this
problem
    when rebalance is in progress and peer probe is executed rebalance op-sm
and
    peer probe may run into race making peerinfo structure go for toss.

    Solution: Use local copy of peer list (xaction_peers) in glusterd op-sm.

    Change-Id: I1ff7118dc6a9a72633e2e87b7ab7bae1796595e0
    BUG: 1152890
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/8932
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas at redhat.com>
    Reviewed-by: Kaushal M <kaushal 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=qxlWoHBgu7&a=cc_unsubscribe