congqixia

Also, we could observe that recovered `LoadBalanceTask` may not make sense in some cases.

@ThreadDao according to the log, there was a release request before the first load operation is done. May I ask what is the expect behavior of this situation?

 Actually there are 2 restart during the test. Looking into it.

Both run querynode restart due to OOMKilled.

Should be fixed by #17828 and #17738 Could you please verify? /assign @jingkl /unassign

`test-etcd-no-clean-vf5jt-1-milvus-querynode-5bf8696f45-nr75s` was OOMKilled. Checked the growing releasing ran normally in according to the log.

@jiaoew1991 FYI, querynode cannot provide sevice after restart due to an imcompleted SyncReplicaSegments call.

OK, I shall check the current implementation when drop a partition which is loaded.

Here are some behavior for drop partition when the collection is loaded: - As @yanliang567 mentioned, the Partition is not automatically released if it's loaded - The deleted partition data...

/approve