mirror of https://github.com/milvus-io/milvus.git
issue: #45847 After a collection is successfully loaded, the shard-leader state on the QC may still not be marked as serviceable. It becomes serviceable only after the scheduled distribution update runs, which will also invalidate the shard-leader cache on the proxy. Therefore, even if queries are already executable, the shard-leader mapping on the proxy may still change afterward. Try to ensure—as much as possible—that the proxy’s shard-leader cache remains stable before killing the mixcoord. Signed-off-by: Cai Zhang <cai.zhang@zilliz.com> |
||
|---|---|---|
| .. | ||
| search_after_coord_down_test.go | ||