Vnode moved to another dnode or was deleted

General Questions
问题：数据文件中的Vnode移动或是被删除需要怎么处理

数据库版本: 3.0.2.5

查询日志显示：

tail -n 100 taosdlog,0
more 12/04 13:11:31.340781 00001880 DND ERROR vgId:28, msg:0x7f73fc002e98 failed to put into vnode queue since Vnode moved to another dnode or was deleted, type:vnode-drop-stb qtype:3 contLen:36, gtid:0x0:0x27d40333d19073c7 12/04 13:11:32.963736 00002161 SYN vgId:42, fsm execute vnode commit. index:6624983, term:27 12/04 13:11:32.963820 00002163 VND vgId:42, commit at version 6624983 12/04 13:11:32.965211 00002163 VND vgId:42, vnode info is saved, fname:/alidata/taos/data/vnode/vnode42/vnode_tmp.json replica:3 selfIndex:0 12/04 13:11:32.965551 00002163 VND vgId:42, vnode async commit done, commitId:95993 term:27 applied:6624983 12/04 13:11:32.965594 00001980 VND vgId:42, start to commit, commitId:95993 version:6624983 term: 27 12/04 13:11:32.976508 00001980 TSD vgId:42, tsdb end commit 12/04 13:11:32.977127 00001980 VND vgId:42, vnode info is committed 12/04 13:11:32.977565 00001980 TSD vgId:42, tsdb finish commit 12/04 13:11:32.979096 00001980 VND vgId:42, commit end 12/04 13:11:33.343546 00001878 DND ERROR vgId:28, msg:0x7f73f4000c18 failed to put into vnode queue since Vnode moved to another dnode or was deleted, type:vnode-drop-stb qtype:3 contLen:36, gtid:0x0:0x27d40333d200741d 12/04 13:11:35.346863 00001881 DND ERROR vgId:28, msg:0x7f73f00076f8 failed to put into vnode queue since Vnode moved to another dnode or was deleted, type:vnode-drop-stb qtype:3 contLen:36, gtid:0x0:0x27d40333d2807463 12/04 13:11:37.350100 00001878 DND ERROR vgId:28, msg:0x7f73f40010c8 failed to put into vnode queue since Vnode moved to another dnode or was deleted, type:vnode-drop-stb qtype:3 contLen:36, gtid:0x0:0x27d40333d30074b5 more

Start by reviewing the taosdlog entries for vgId 28 and the vnode-drop-stb messages, using the reported TDengine version 3.0.2.5 as context. Determine whether the vnode was moved or deleted and document the appropriate handling or diagnosis; the issue is done when the cause and next steps are clear.