How reproducible: ================= 1/1 Steps to Reproduce: =================== 1. Create 2*2 setup spanning on 4 storage server (server1 to server4) 2. Offline the brick process by killing its pid on server1 3. Poweroff server3 4. Noticed server1 brick process is online again Actual results: =============== Process should still be offline. Log-snippet step by step 1. Volume type: distributed replicate 2. Volume status and their pid 3. Killed the brick process on server1 using "kill -9 <pid>" 4. Volume status confirms that the brick is offline 5. Powered down the server3 using poweroff 6. Executed command gluster volume status which shows the process is Online Expected results: ================= It should not start the offline process of different server1.
REVIEW: http://review.gluster.org/4954 (mgmt/glusterd: Prevent spurious brick restarts) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/4955 (mgmt/glusterd: Perform Pending quorum actions after Op) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/4954 (mgmt/glusterd: Prevent spurious brick restarts) posted (#4) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/4955 (mgmt/glusterd: Perform Pending quorum actions after Op) posted (#4) for review on master by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/4955 committed in master by Kaushal M (kaushal) ------ commit a4b622e0bd60a5e19e73f415a6a64aa6661a971a Author: Pranith Kumar K <pkarampu> Date: Mon May 5 11:28:25 2014 +0530 mgmt/glusterd: Perform Pending quorum actions after Op Change-Id: I2bb67b5fb4a6f6dac892ef3206e7a79706018a6e BUG: 959986 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/4955 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal>
COMMIT: http://review.gluster.org/4954 committed in master by Kaushal M (kaushal) ------ commit 281d95cb7d53069158eae99392e9e7863c8850fd Author: Pranith Kumar K <pkarampu> Date: Mon May 5 11:29:12 2014 +0530 mgmt/glusterd: Prevent spurious brick restarts Change-Id: I7ee5d18b926d6c31e3e4ea2f5fbe9050c8e1dee8 BUG: 959986 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/4954 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Kaushal M <kaushal>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users