Bug 1431192 - [RFE] Gluster get state command should provide volume and cluster utilization related information
Summary: [RFE] Gluster get state command should provide volume and cluster utilization...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Samikshan Bairagya
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1488018
TreeView+ depends on / blocked
 
Reported: 2017-03-10 14:52 UTC by Darshan
Modified: 2017-09-04 06:37 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.11.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1488018 (view as bug list)
Environment:
Last Closed: 2017-05-30 18:47:11 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Darshan 2017-03-10 14:52:34 UTC
Description of problem:
Currently "gluster get-state" command does not give any volume and cluster usage related information. It should give information about the usage of volume and cluster like what is the full size of a volume/cluster and how much of it is currently full. Also it should give the status of cluster just like gstatus(https://github.com/gluster/gstatus) tool provides

Version-Release number of selected component (if applicable):
3.9

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
If its very costly to provide this information please enhance gluster get-state to take an option something like "--detail". When "--detail" is provided get-state must provide all the details including the ones which are costly to fetch. Without this option it should only give information which are not costly.

This is needed for tendrl project: https://redhat.invisionapp.com/share/589XIRJBW#/screens/213318639

Comment 1 Samikshan Bairagya 2017-03-15 11:35:18 UTC
This is what the gstatus README says:

"Capacity information is derived from the brick information taken from a 'vol status detail' command. The accuracy of this number therefore depends on the nodes/bricks being all up - elements missing from the configuration will simply be missing from the calculation."

The get-state CLI doesn't intend to aggregate results from individual nodes to provide a cluster level result like gstatus does. What get-state can do is provide the per-node information needed to compute the required data like volume and cluster utilisation on another layer.

Comment 2 Worker Ant 2017-04-10 13:18:12 UTC
REVIEW: https://review.gluster.org/17029 (glusterd: Add brick capacity details to get-state CLI output) posted (#1) for review on master by Samikshan Bairagya (samikshan)

Comment 3 Worker Ant 2017-04-14 18:14:39 UTC
REVIEW: https://review.gluster.org/17029 (glusterd: Add brick capacity details to get-state CLI output) posted (#2) for review on master by Samikshan Bairagya (samikshan)

Comment 4 Worker Ant 2017-04-15 01:40:51 UTC
COMMIT: https://review.gluster.org/17029 committed in master by Atin Mukherjee (amukherj) 
------
commit c09f5a28bfd14066f9b8cfca53c7a9d999f1613e
Author: Samikshan Bairagya <samikshan>
Date:   Mon Apr 10 18:46:42 2017 +0530

    glusterd: Add brick capacity details to get-state CLI output
    
    Change-Id: I53fe180e71d41d56b129254b93bb74014a2cdb43
    BUG: 1431192
    Signed-off-by: Samikshan Bairagya <samikshan>
    Reviewed-on: https://review.gluster.org/17029
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Atin Mukherjee <amukherj>

Comment 5 Shyamsundar 2017-05-30 18:47:11 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.11.0, please open a new bug report.

glusterfs-3.11.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://lists.gluster.org/pipermail/announce/2017-May/000073.html
[2] https://www.gluster.org/pipermail/gluster-users/


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