Description of problem: After detach tier start, detach tier status is used to check the status of migration and the number of files being migrated. Although the detach tier is in progress and files are being migrated, the statistics are not updated. The info on 'rebalanced-files' is updated only after detach tier operation is completed. [root@dhcp37-120 ~]# gluster v tier superman detach status Node Rebalanced-files size scanned failures skipped status run time in h:m:s --------- ----------- ----------- ----------- ----------- ----------- ------------ -------------- localhost 0 0Bytes 0 0 0 in progress 0:0:0 10.70.37.60 0 0Bytes 0 0 0 in progress 0:0:0 10.70.37.101 0 0Bytes 0 0 0 in progress 0:0:0 10.70.35.133 0 0Bytes 0 0 0 in progress 0:0:0 10.70.35.239 0 0Bytes 0 0 0 in progress 0:0:0 10.70.35.225 0 0Bytes 0 0 0 in progress 0:0:0 10.70.35.11 0 0Bytes 0 0 0 in progress 0:0:0 10.70.35.10 0 0Bytes 0 0 0 in progress 0:0:0 Version-Release number of selected component (if applicable): glusterfs-server-3.7.9-4.el7rhgs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a tiered volume 2. Have few files in hot tier 3. Run 'detach tier start' 4. check the status of detach tier operation using 'detach tier status' Actual results: Info on 'rebalanced-files' is not updated Expected results: There is no way for a user to know on the number of files being migrated and moved to cold tier. This information has to get updated on the go. Additional info:
The __glusterd_defrag_notify is called once the existing tier process goes down. the new process for demoting the files has a volinfo->rebal.defrag and this is set to NULL by the previous process going down as both use the same volinfo->rebal.defrag. As the defrag is not available the rpc connection doesn't work and so the detach status doesn't get the value to update.
Thank you for your bug report. We are no longer working on any improvements for Tier. This bug will be set to CLOSED WONTFIX to reflect this. Please reopen if the rfe is deemed critical.