-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Too many L0 segments caused query node OOM. #33278
Comments
More error logs for reference. [2024/05/22 06:48:08.854 +00:00] [INFO] [task/scheduler.go:591] ["processed tasks"] [nodeID=1012] [toProcessNum=0] [committedNum=0] [toRemoveNum=0] |
/assign @XuanYang-cn |
Dup with #36953 Closing this issue |
Is there an existing issue for this?
Environment
Current Behavior
We use upserts to ingest data to milvus, which will generate many deletes messages. If the delete messages are not consumed in time, seems a lot of L0 segments will be generated. If we restart query node which is used for growing segment, it will try to create tasks for all those L0 segments and meet OOM.
Expected Behavior
The L0 segments loading should not cause the query node to be oom killed.
Steps To Reproduce
Milvus Log
[2024/05/22 06:48:09.430 +00:00] [INFO] [task/scheduler.go:281] ["task added"] [task="[id=1716360317352] [type=Grow] [source=segment_checker] [reason=lacks of segment] [collectionID=449821998347640028] [replicaID=449933559028252673] [resourceGroup=__default_resource_group] [priority=Normal] [actionsCount=1] [actions={[type=Grow][node=1017][streaming=false]}] [segmentID=449821998398092289]"]
[2024/05/22 06:48:09.430 +00:00] [INFO] [task/scheduler.go:281] ["task added"] [task="[id=1716360317353] [type=Grow] [source=segment_checker] [reason=lacks of segment] [collectionID=449821998347640028] [replicaID=449933559028252673] [resourceGroup=__default_resource_group] [priority=Normal] [actionsCount=1] [actions={[type=Grow][node=1017][streaming=false]}] [segmentID=449821998398499739]"]
[2024/05/22 06:48:09.430 +00:00] [INFO] [task/scheduler.go:281] ["task added"] [task="[id=1716360317354] [type=Grow] [source=segment_checker] [reason=lacks of segment] [collectionID=449821998347640028] [replicaID=449933559028252673] [resourceGroup=__default_resource_group] [priority=Normal] [actionsCount=1] [actions={[type=Grow][node=1017][streaming=false]}] [segmentID=449821998414241025]"]
[2024/05/22 06:48:09.430 +00:00] [INFO] [task/scheduler.go:281] ["task added"] [task="[id=1716360317355] [type=Grow] [source=segment_checker] [reason=lacks of segment] [collectionID=449821998347640028] [replicaID=449933559028252673] [resourceGroup=__default_resource_group] [priority=Normal] [actionsCount=1] [actions={[type=Grow][node=1017][streaming=false]}] [segmentID=449821998414849387]"]
Anything else?
No thanks.
The text was updated successfully, but these errors were encountered: