-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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]: QueryNode oomkilled due to sudden increase in the number of growing segments #34554
Open
1 task done
Labels
kind/bug
Issues or changes related a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Comments
/assign @congqixia |
Previous test result: |
Previous test result: argo: https://argo-workflows.zilliz.cc/archived-workflows/qa/8c535d6e-68ea-4dc3-ac49-13772107181f?nodeId=level-zero-stable-1720105200-try-2485191624 |
/assign @bigsheeper |
sre-ci-robot
pushed a commit
that referenced
this issue
Jul 17, 2024
Seals the largest growing segment if the total size of growing segments of each shard exceeds the size threshold(default 4GB). Introducing this policy can help keep the size of growing segments within a suitable level, alleviating the pressure on the delegator. issue: #34554 --------- Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
bigsheeper
added a commit
to bigsheeper/milvus
that referenced
this issue
Jul 18, 2024
Seals the largest growing segment if the total size of growing segments of each shard exceeds the size threshold(default 4GB). Introducing this policy can help keep the size of growing segments within a suitable level, alleviating the pressure on the delegator. issue: milvus-io#34554 --------- Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
sre-ci-robot
pushed a commit
that referenced
this issue
Jul 19, 2024
Seals the largest growing segment if the total size of growing segments of each shard exceeds the size threshold(default 4GB). Introducing this policy can help keep the size of growing segments within a suitable level, alleviating the pressure on the delegator. issue: #34554 pr: #34692 --------- Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Issues or changes related a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Is there an existing issue for this?
Environment
Current Behavior
deploy milvus
deploy
level-zero-insert-op-96-4610
with 4 queryNodestest
results
queryNode (one of delegator oomkilled)
![image](https://cdn.statically.io/img/private-user-images.githubusercontent.com/27288593/347246294-e9d597fe-e476-47d3-b125-295ab2d6eb18.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE5NjkwMjMsIm5iZiI6MTcyMTk2ODcyMywicGF0aCI6Ii8yNzI4ODU5My8zNDcyNDYyOTQtZTlkNTk3ZmUtZTQ3Ni00N2QzLWIxMjUtMjk1YWIyZDZlYjE4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI2VDA0Mzg0M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTQ3N2M5MTQ5NGJlODk0NzJjYTVmZGMyOTk3YmUxNjVhODQ1OWJmMTBhZGMxNGIwZjY3ZGIwZmIwMTEyOTBjNTQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.yKRSuS7kP3EUBiZ3J1HxNcVRM-d46QtRII23E-FYzzM)
metrics of level-zero-insert-op-96-4610
Expected Behavior
No response
Steps To Reproduce
https://argo-workflows.zilliz.cc/archived-workflows/qa/dff50b01-bbe4-4995-970d-db19181d2f12?nodeId=level-zero-stable-1720537200-171318015
Milvus Log
pods:
Anything else?
No response
The text was updated successfully, but these errors were encountered: