Bug 1064802

Summary: DHT + rebalance : rebalance status output is ambiguous need to define behaviour in case of failures
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Rachana Patel <racpatel>
Component: distributeAssignee: Nithya Balachandran <nbalacha>
Status: CLOSED DEFERRED QA Contact: storage-qa-internal <storage-qa-internal>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.1CC: mzywusko, nlevinki, spalai, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1286125 (view as bug list) Environment:
Last Closed: 2015-11-27 11:36:58 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:
Bug Depends On:    
Bug Blocks: 1286125    

Description Rachana Patel 2014-02-13 10:39:12 UTC
Description of problem:
rebalance status is  ambiguous In case of Failures,
e.g.
1)
[root@OVM2 ~]# gluster volume rebalance dht1 status
                                    Node Rebalanced-files          size       scanned      failures       skipped               status   run time in secs
                               ---------      -----------   -----------   -----------   -----------   -----------         ------------     --------------
                               localhost            55722         1.1GB        197894            29             1            completed            5177.00
                            10.70.35.228            52862       988.4MB        172572            27             3            completed            5084.00
                            10.70.35.212              308        51.3MB       3543049             0             0            completed           25631.00
volume rebalance: dht1: success: 


even though failure column has xx count, status says 'completed'.

2) as mentioned in bug 1064481 rebalance process hasn't completed crawl but status shows completed

Version-Release number of selected component (if applicable):
3.4.0.59rhs-1.el6rhs.x86_64

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
need clarification on rebalance status:-
- In which Cases 'status' column should show 'failed' or 'completed'
- 'failures' column should show count of file migration failures only or should include Directory layout fixing failures also.



Additional info:

Comment 3 Susant Kumar Palai 2015-11-27 11:36:58 UTC
Cloning this to 3.1. To be fixed in future.