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. Version-Release number of selected component (if applicable): 3.10 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/AB94BNET6#/screens/221686840
(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