+++ This bug was initially created as a clone of Bug #1276675 +++ Description of problem: Problem: 1) Glusterd doesn't remember about arbiter information of replica volume in store. When glusterd goes down and comes backup, arbiter volumes will become replica volumes. 2) Glusterd doesn't import/export arbiter information to/from the other peers. 3) Volume info doesn't show any arbiter count in the output. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Vijay Bellur on 2015-10-30 09:11:31 EDT --- REVIEW: http://review.gluster.org/12475 (mgmt/glusterd: Store arbiter-count and restore it) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu) --- Additional comment from Vijay Bellur on 2015-11-01 01:20:19 EST --- REVIEW: http://review.gluster.org/12475 (mgmt/glusterd: Store arbiter-count and restore it) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu) --- Additional comment from Vijay Bellur on 2015-11-01 02:32:53 EST --- REVIEW: http://review.gluster.org/12475 (mgmt/glusterd: Store arbiter-count and restore it) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)
REVIEW: http://review.gluster.org/12479 (mgmt/glusterd: Store arbiter-count and restore it) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)
COMMIT: http://review.gluster.org/12479 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) ------ commit 60a4288f0a2444821e17ac6eaeb402b466dd4a1a Author: Pranith Kumar K <pkarampu> Date: Fri Oct 30 15:56:14 2015 +0530 mgmt/glusterd: Store arbiter-count and restore it Backport of http://review.gluster.com/12475 Problem: 1) Glusterd doesn't remember about arbiter information of replica volume in store. When glusterd goes down and comes backup, arbiter volumes will become replica volumes. 2) Glusterd doesn't import/export arbiter information to/from the other peers. 3) Volume info doesn't show any arbiter count in the output. Fix: 1) Persist arbiter information in glusterd-store 2) Import/Export arbiter information of the volume 3) Change volume info output to show arbiter count. >Change-Id: I2db81e73d2694b01f7d07b08a17b41ad5a55c361 >BUG: 1276675 >Signed-off-by: Pranith Kumar K <pkarampu> BUG: 1276907 Change-Id: I95c9857d645e02831892092bdd07539cc1a58270 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/12479 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Ravishankar N <ravishankar> Tested-by: Gluster Build System <jenkins.com>
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.7, please open a new bug report. glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user