Bug 1431187
Summary: | [RFE] Gluster get state command should provide rebalance related information | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Darshan <dnarayan> |
Component: | glusterd | Assignee: | Samikshan Bairagya <sbairagy> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | amukherj, bugs |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-03-21 14:50:16 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Darshan
2017-03-10 14:43:59 UTC
(In reply to Darshan from comment #0) > Description of problem: > Currently "gluster get-state" command gives only some information about > rebalance that happened on a particular volume. It should give fill > information about the on going / past reblance on the volume(like things > provided by "volume rebalance status" command), along with other volume > details. Currently gluster volume rebalance status gives the following information: # gluster volume rebalance <volname> status Node Rebalanced-files size scanned failures skipped status run time in h:m:s --------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- localhost 0 0Bytes 1 0 0 completed 0:00:00 192.168.122.31 0 0Bytes 0 0 0 completed 0:00:00 192.168.122.189 0 0Bytes 1 0 0 completed 0:00:00 The get-state CLI currently gives the following information per node per volume for rebalance ops: - id - status - failures - skipped - lookedup - rebalanced files - data size The above information seems to sufficiently cover all the data points as seen here: https://redhat.invisionapp.com/share/AB94BNET6#/screens/221686840. The only information missing here is the run-time. If that is required, we can add that; else, the get-state CLI in its current form provides sufficient node-level information which when aggregated by external agents will provide a cluster wide view of the rebalance status. Hence I am closing this bug. Will reopen if I need to add the run-time related information to the get-state output |