Description of problem: 'gluster volume rebalace status' displays 'rebalance completed!' before completing the rebalance. Version-Release number of selected component (if applicable): git master with head at 5fdd65f5f4f5df1d28b0fb4f7efed226d5db1b3c How reproducible: Often Steps to Reproduce: 1. Create a 1 node distribute volume. 2. Create some data like untar the linux kernel1 3. Add one more brick using add-brick 4. Run 'rebalance start' and 'rebalance status' immediately Actual results: 'rebalance status' displays rebalance completed, but rebalance is not completed yet. Expected results: rebalance status should say which file is being moved and 'rebalance completed' should be displayed only after successful completion of rebalance. Additional info:
Were bricks on the same node? If not, as of now if rebalance completes on the node where the command was issued, we get the status as completed, even if the migration is in progress.
(In reply to comment #1) > Were bricks on the same node? > If not, as of now if rebalance completes on the node where the command was > issued, we get the status as completed, even if the migration is in progress. I issued the rebalance command on the node which had the newly added brick. After the 'rebalance completed' message is displayed, 'du -sh' on the back-end export of same node started increasing. So migration on that node was still happening when rebalance completed was displayed.
This is a know issue, and a constraint right now. The parallel rebalance now is a push operation, i.e, rebalance process of the src node is the actual worker in this case. Hence the rebalance process on the dst ran to completion, as it does not do actual migration. We can keep this bug open, as we need to handle this issue.
CHANGE: http://review.gluster.com/2942 (dht: Rebalance status should display status from each process) merged in master by Vijay Bellur (vijay)
Now rebalance status is displayed for each node in the cluster. Moving to verified.