mirror of https://github.com/milvus-io/milvus.git
b08d9efe69
issue: #42098 #42404 pr: #42689 Fix critical issue where concurrent balance segment and balance channel operations cause delegator view inconsistency. When shard leader switches between load and release phases of segment balance, it results in loading segments on old delegator but releasing on new delegator, making the new delegator unserviceable. The root cause is that balance segment modifies delegator views, and if these modifications happen on different delegators due to leader change, it corrupts the delegator state and affects query availability. Changes include: - Add shardLeaderID field to SegmentTask to track delegator for load - Record shard leader ID during segment loading in move operations - Skip release if shard leader changed from the one used for loading - Add comprehensive unit tests for leader change scenarios This ensures balance segment operations are atomic on single delegator, preventing view corruption and maintaining delegator serviceability. --------- Signed-off-by: Wei Liu <wei.liu@zilliz.com> |
||
|---|---|---|
| .. | ||
| hash.go | ||
| hash_test.go | ||
| mock_task.go | ||
| pool.go | ||
| pool_test.go | ||
| scheduler.go | ||
| scheduler_test.go | ||
| task.go | ||
| task_import.go | ||
| task_l0_import.go | ||
| task_l0_import_test.go | ||
| task_l0_preimport.go | ||
| task_manager.go | ||
| task_manager_test.go | ||
| task_preimport.go | ||
| util.go | ||
| util_test.go | ||