[Bugs] [Bug 1352926] New: gluster volume status <volume> client" isn' t showing any information when one of the nodes in a 3-way Distributed-Replicate volume is shut down
bugzilla at redhat.com
bugzilla at redhat.com
Tue Jul 5 13:53:01 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1352926
Bug ID: 1352926
Summary: gluster volume status <volume> client" isn't showing
any information when one of the nodes in a 3-way
Distributed-Replicate volume is shut down
Product: GlusterFS
Version: 3.8.0
Component: cli
Keywords: Triaged
Severity: low
Assignee: bugs at gluster.org
Reporter: amukherj at redhat.com
CC: bugs at gluster.org, ccalhoun at redhat.com,
storage-qa-internal at redhat.com
Depends On: 1351732, 1351880
+++ This bug was initially created as a clone of Bug #1351880 +++
+++ This bug was initially created as a clone of Bug #1351732 +++
Description of problem:
3-way Distributed-Replicate volume...
[root at node1 ~]# gluster volume status vol1
Status of volume: vol1
Gluster process TCP Port RDMA Port Online Pid
------------------------------------------------------------------------------
node1:brick1 49165 0 Y 3665
node2:brick2 49164 0 Y 17094
node3:brick3 49154 0 Y 19888
node1:brick4 49172 0 Y 3670
node2:brick5 49171 0 Y 17099
node3:brick6 49155 0 Y 19907
NFS Server on localhost 2049 0 Y 3679
Self-heal Daemon on localhost N/A N/A Y 3689
NFS Server on node3 2049 0 Y 19927
Self-heal Daemon on node3 N/A N/A Y 19935
NFS Server on node2 2049 0 Y 20374
Self-heal Daemon on node2 N/A N/A Y 20382
Task Status of Volume vol1
------------------------------------------------------------------------------
There are no active volume tasks
[root at node1 ~]#
If the first node in the cluster is shut down, the one where the volume was
created and started from, when I try and display on the two remaining nodes
information about the clients connected to the volume I don't get any
information back.
[root at node2 glusterfs]# gluster volume status vol1 client
Client connections for volume vol1
----------------------------------------------
----------------------------------------------
[root at node3 glusterfs]# gluster volume status vol1 clients
Client connections for volume vol1
----------------------------------------------
----------------------------------------------
As soon as the node (node1) is powered back up and everything is up and running
again, the clients are visible.
==========
Version-Release number of selected component (if applicable):
All nodes:
gluster-nagios-addons-0.2.5-1.el7rhgs.x86_64
gluster-nagios-common-0.2.3-1.el7rhgs.noarch
glusterfs-3.7.5-19.el7rhgs.x86_64
glusterfs-api-3.7.5-19.el7rhgs.x86_64
glusterfs-cli-3.7.5-19.el7rhgs.x86_64
glusterfs-client-xlators-3.7.5-19.el7rhgs.x86_64
glusterfs-fuse-3.7.5-19.el7rhgs.x86_64
glusterfs-geo-replication-3.7.5-19.el7rhgs.x86_64
glusterfs-libs-3.7.5-19.el7rhgs.x86_64
glusterfs-rdma-3.7.5-19.el7rhgs.x86_64
glusterfs-server-3.7.5-19.el7rhgs.x86_64
python-gluster-3.7.5-19.el7rhgs.noarch
samba-vfs-glusterfs-4.2.4-13.el7rhgs.x86_64
vdsm-gluster-4.16.30-1.3.el7rhgs.noarch
==========
How reproducible:
Completely
==========
Steps to Reproduce:
See description
--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-06-30
12:55:26 EDT ---
This bug is automatically being proposed for the current z-stream release of
Red Hat Gluster Storage 3 by setting the release flag 'rhgs‑3.1.z' to '?'.
If this bug should be proposed for a different release, please manually change
the proposed release flag.
--- Additional comment from Atin Mukherjee on 2016-07-01 01:43:09 EDT ---
RCA:
In CLI side the response dictionary is parsed assuming all the bricks to be up.
Since in this case one of the node was brought down client details for the
bricks hosted by the same node were not available in the dictionary resulting
into a blank output for 'gluster volume status <volname> clients'
--- Additional comment from Vijay Bellur on 2016-07-01 02:21:00 EDT ---
REVIEW: http://review.gluster.org/14842 (cli: print volume status client output
for partial bricks) posted (#1) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Vijay Bellur on 2016-07-05 07:45:40 EDT ---
COMMIT: http://review.gluster.org/14842 committed in master by Jeff Darcy
(jdarcy at redhat.com)
------
commit 427ef5511232614bafcab686ad797cebb6a2d6b5
Author: Atin Mukherjee <amukherj at redhat.com>
Date: Fri Jul 1 11:47:48 2016 +0530
cli: print volume status client output for partial bricks
In cli the response dictionary is parsed assuming all the bricks to be up.
If in a given cluster one of the node is down client details for the
bricks hosted by the same node are not available in the dictionary
resulting
into a blank output for 'gluster volume status <volname> clients'
Fix is to ignore the ret value for dict_get for those keys.
Change-Id: If4fb65b8807ea3ac71b3ed1a754ea75f599e3613
BUG: 1351880
Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-on: http://review.gluster.org/14842
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Jeff Darcy <jdarcy at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1351732
[Bug 1351732] gluster volume status <volume> client" isn't showing any
information when one of the nodes in a 3-way Distributed-Replicate volume
is shut down
https://bugzilla.redhat.com/show_bug.cgi?id=1351880
[Bug 1351880] gluster volume status <volume> client" isn't showing any
information when one of the nodes in a 3-way Distributed-Replicate volume
is shut down
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list