Zhen Ye
Zhen Ye
It's a part of Resource Group Enhancement PR. Resource Group Enhancement PR is too large, split it into multi-part to review easily.
/assign @chyezh
Index `447990444064979058` belongs to Segment `447990444064723266`. Node `` start to release segment while new load request is incoming. ``` [2024/02/26 16:13:34.948 +00:00] [INFO] [querynodev2/services.go:595] ["start to release segments"] [traceID=06cd8e504609e669a530c57535e33631] [collectionID=447902879639453431]...
Short-term fix: Implement mutual exclusivity between Release and Load on QN; Long-term, it is necessary to implement lifecycle controls such as Loading, Loaded, Release state of Segment on QueryCoord.
> @chyezh Loading segment will not be released in segment manager. In my opinion, concurrent load&release shall not happen for same segment. Could you please explain the detail how it...
> After some offline discussion, the final solution shall be separating the disk resource for different segment life-cycle. > > One more thing, it's looks weird that a segment is...
Release then load collection. Or concurrent release and load collection can reproduce it. ``` 2024-02-27 00:13:34.487 [2024/02/26 16:13:34.487 +00:00] [INFO] [querycoordv2/services.go:254] ["release collection request received"] [traceID=458948ca161f98b29f6d8118b6001ae5] [collectionID=447902879639453431] 2024-02-27 00:13:34.498 [2024/02/26...
/run-cpu-e2e
/run-cpu-e2e