Bug 1152890 - Peer probe during rebalance causing "Peer rejected" state for an existing node in trusted cluster
Summary: Peer probe during rebalance causing "Peer rejected" state for an existing no...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Atin Mukherjee
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1138547
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-15 07:14 UTC by Atin Mukherjee
Modified: 2015-05-14 17:44 UTC (History)
6 users (show)

Fixed In Version: glusterfs-3.7.0
Doc Type: Bug Fix
Doc Text:
Clone Of: 1138547
Environment:
Last Closed: 2015-05-14 17:27:58 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Anand Avati 2014-10-15 07:50:58 UTC
REVIEW: http://review.gluster.org/8932 (glusterd: op state machine shouldn't use global peer list) posted (#1) for review on master by Atin Mukherjee (amukherj)

Comment 2 Anand Avati 2014-10-17 09:55:01 UTC
REVIEW: http://review.gluster.org/8932 (glusterd: op state machine shouldn't use global peer list) posted (#2) for review on master by Atin Mukherjee (amukherj)

Comment 3 Anand Avati 2014-10-21 06:19:24 UTC
REVIEW: http://review.gluster.org/8932 (glusterd: op state machine shouldn't use global peer list) posted (#3) for review on master by Atin Mukherjee (amukherj)

Comment 4 Anand Avati 2014-10-29 06:58:44 UTC
COMMIT: http://review.gluster.org/8932 committed in master by Kaushal M (kaushal) 
------
commit 8df26e838c40f15bb2b26131d1533da339f5be3e
Author: Atin Mukherjee <amukherj>
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>
    Reviewed-on: http://review.gluster.org/8932
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krishnan Parthasarathi <kparthas>
    Reviewed-by: Kaushal M <kaushal>

Comment 5 Niels de Vos 2015-05-14 17:27:58 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 6 Niels de Vos 2015-05-14 17:35:39 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 7 Niels de Vos 2015-05-14 17:38:00 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

Comment 8 Niels de Vos 2015-05-14 17:44:09 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report.

glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user


Note You need to log in before you can comment on or make changes to this bug.