Red Hat Bugzilla – Bug 1351185
[GSS] - RFE: Add info on op-version for clients in vol status output in order to ease client and server version compatibility
Last modified: 2017-09-21 00:54:54 EDT
upstream patch : http://review.gluster.org/16303
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/101289/
verified in 3.8.4.22 No such command for now, but we can check from the glusterd statedump, if the client falls in min and max op-version then it is compatible otherwise not. Here from glusterd statedump glusterd.client6.identifier=10.70.37.218:1021 glusterd.client6.volname=third glusterd.client6.max-op-version=31001 glusterd.client6.min-op-version=1 Hence marking it as verified
Bipin thanks for the info to verify the RFE/bug "gluster vol status new1 clients" is the command to check the opversion, bytesread and byteswritten on the bricks and number of clients connected. For a volume [root@dhcp37-135 new1]# gluster vol status new1 clients Client connections for volume new1 ---------------------------------------------- Brick : dhcp37-135:/bricks/brick3/new990 Clients connected : 2 Hostname BytesRead BytesWritten OpVersion -------- --------- ------------ --------- 10.70.37.218:1020 187520 152860 31001 10.70.37.101:1019 2864 2260 31001 ---------------------------------------------- Brick : dhcp37-138:/bricks/brick3/new2 Clients connected : 2 Hostname BytesRead BytesWritten OpVersion -------- --------- ------------ --------- 10.70.37.218:1018 193980 158920 31001 10.70.37.101:1017 2428 1936 31001 ---------------------------------------------- Brick : dhcp37-140:/bricks/brick3/new993 Clients connected : 2 Hostname BytesRead BytesWritten OpVersion -------- --------- ------------ --------- 10.70.37.218:1017 189648 154996 31001 10.70.37.101:1016 2432 1936 31001 ----------------------------------------------
verified in 3.8.4.23
Note: As the code changes are made in clientside. So if we use previous version clients like 3.2 or 3.13. The opversion by default will be shown as 0. It won't fetch the opversion from earlier versioned clients. This change will help to fetch client opversion from 3.3 and further. Below I used 3.2 clients that's why under the opversion its is shown as 0 [root@dhcp37-135 new1]# gluster vol status new1 clients Client connections for volume new1 ---------------------------------------------- Brick : dhcp37-135:/bricks/brick3/new990 Clients connected : 2 Hostname BytesRead BytesWritten OpVersion -------- --------- ------------ --------- 10.70.35.161:1019 2104 1704 0 10.70.35.161:1010 1676 1328 0 ---------------------------------------------- Brick : dhcp37-138:/bricks/brick3/new2 Clients connected : 1 Hostname BytesRead BytesWritten OpVersion -------- --------- ------------ --------- 10.70.35.161:1017 1668 1328 0 ---------------------------------------------- Brick : dhcp37-140:/bricks/brick3/new993 Clients connected : 1 Hostname BytesRead BytesWritten OpVersion -------- --------- ------------ --------- 10.70.35.161:1011 1672 1328 0 ---------------------------------------------- Brick : dhcp37-135:/bricks/brick1/new_brick Clients connected : 2 Hostname BytesRead BytesWritten OpVersion -------- --------- ------------ --------- 10.70.35.161:1019 2104 1704 0 10.70.35.161:1010 1676 1328 0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2774