Why does performance degradation and collection loading & release failure occur due to entity upsert? #40408
Replies: 1 comment 5 replies
-
upsert = delete + insert Datanode triggers compaction actions to erase entities by the IDs from L0 segment. The empty L0 segments mean their IDs have been processed. Empty L0 segments will be remove by GC(garbage collection) of milvus. GC action is triggered with an interval of 1 hour. Intensive/continually upsert action will downgrade search performance because it is a heavier operation than normal insert. The log doesn't show the root cause why load() timeout. |
Beta Was this translation helpful? Give feedback.
-
Hi.
I am running Milvus v2.4.23 on kubernetes using helm chart.
When using entity upsert, Empty segments (L0) are created in the collection.
As a resut, Timeout occur during Milvus collection loading and release.
As the same time, The performance of Milvus search degrades for all collections including othres.
DataCoord Logs
QueryCoord Logs
Birdwatcher
cf. I have removed the logs for the other collections.
Q1. Why does empty segments (L0) appear when performing an entity upsert?
Q2. When are empty segments (L0) removed?
Q3. How can i solve this issue? I need a help..
Beta Was this translation helpful? Give feedback.
All reactions