Zhen Ye

 The mixcoord is not startup while the old distributed coordinator is not down. The querynode is rolling update, and the segment and channel cannot be moved by old querycoord....

By confirmed by @haorenfsa We only support upgrade a 2.5 cluster with mixcoord to 2.6. If user want to upgrade a 2.5 cluster with distributed coord to 2.6, user need...

When the search latency increasing, the following search segments operation is applied on target querynode. The following 8 search operation is blocked by the search segment `453736378046070459`, and the concurrency...

By adding new log and attach trace_id into logs. Found that high time cost at delete. ``` 2024-11-12 17:20:33.340 I20241112 09:20:33.339989 262 ExecPlanNodeVisitor.cpp:249] [SERVER][VectorVisitorImpl][MILVUS_FUTURE_C][652d52ef3d7d73dcef3842aeac58069b]xxx search scalar cost:565.016, vector_cost:8297.627, get_active cost:...

I think that: Why not generate the mask when insert/delete operation incoming. Just store the timestamp/delete mask with different version (ts). Then search or query operation just do a binary...

> for opt 1, sealed segment is safe to implement. growing segment is doable with opt3 ts WDYGT? I think opt3 is good choice for both sealed and growing, (mask,...

It seems that it's introduced by the implementation of partial result. /assign @weiliu1031 please help to check it.

@zhuwenxing Is these issue reproduced?

/assign chyezh

load segment has been done. [2024/08/14 09:37:54.495 +00:00] [INFO] [querynodev2/services.go:492] ["load segments done..."] [traceID=5ed136892591447ab531c9fa37abd7d9] [collectionID=451838354629467151] [partitionID=451838354629467152] [shard=by-dev-rootcoord-dml_1_451838354629467151v0] [segmentID=451838354632090846] [level=L1] [currentNodeID=3] [segments="[451838354632090846]"] load delete data at 09:37:58