Description of problem: While running rebalance on a heterogeneous brick volume, saw failure in rebalance due to "[2019-07-05 09:36:55.653538] E [MSGID: 109039] [dht-common.c:4245:dht_find_local_subvol_cbk] 0-vol6-dht: getxattr err for dir [No data available]" error. How reproducible: 1/1 Steps to Reproduce: 1. Create a 2 brick volume, where brick1 is of 20G and brick2 of 5G 2. Fuse mount the volume on a client node. 3. Check the hash layout on the bricks. 4. Start running I/O from the mount point. 5. While the I/O is still in progress, disable the cluster.weighted-rebalance volume option. 6. Let the I/O continue to run and add-brick of 10G to the volume. 7. Trigger rebalance on the volume. 8. Check hash layout on the back-end bricks. Actual results: Seeing failure in rebalance Expected results: Rebalance should complete successfully.
REVIEW: https://review.gluster.org/23053 (dht: log getxattr failure for node-uuid at \"DEBUG\") posted (#1) for review on master by Susant Palai
This is because of the mismatch in the xattr when it is a pure dist versus a dist-rep or dist-disperse. This should not prevent the rebalance from proceeding.
(In reply to Nithya Balachandran from comment #2) > This is because of the mismatch in the xattr when it is a pure dist versus a > dist-rep or dist-disperse. This should not prevent the rebalance from > proceeding. Correct. But since there was an error logged in dht_find_local_subvol_cbk, it creates confusion that if it is a real error. Just moved the log to DEBUG as the parent function logs if both attempts failed.
(In reply to Susant Kumar Palai from comment #3) > (In reply to Nithya Balachandran from comment #2) > > This is because of the mismatch in the xattr when it is a pure dist versus a > > dist-rep or dist-disperse. This should not prevent the rebalance from > > proceeding. > > Correct. But since there was an error logged in dht_find_local_subvol_cbk, > it creates confusion that if it is a real error. Just moved the log to DEBUG > as the parent function logs if both attempts failed. Then the description is incorrect. "Actual results: Seeing failure in rebalance Expected results: Rebalance should complete successfully." Rebalance will complete successfully. This message does not cause it to stop.
REVIEW: https://review.gluster.org/23053 (dht: log getxattr failure for node-uuid at \"DEBUG\") merged (#3) on master by N Balachandran