-
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]: v2.4.0 query node auto_balance no available #32714
Comments
/assign @sunby |
the attu-client show the error msg follow: show collection failed: load segment failed, OOM if load, maxSegmentSize = 205.4959774017334 MB, memUsage = 121813.59168624878 MB, predictMemUsage = 122019.08766365051 MB, totalMem = 122880 MB thresholdFactor = 0.900000 |
segment: |
@yesyue Could you please refer this doc to export the whole Milvus logs for investigation? |
it seems that you can not load, might be for the unbalance reason. you can use birdwatcher to check if all the segment is sealed or indexed. Using birdwatcher with show segment command can help you to figure out why |
only one query node mem high, and increasing |
Can you provide querynode |
you can use birdwatcher and run |
Is there an existing issue for this?
Environment
Current Behavior
My Collection loading scale of 40 million entites to the mem index. I has enabled 40 query nodes, but the data is only loaded into 2 query nodes. Here is my configuration, how to adjust it to enable automatic memory balancing allocation:
![d034f7bfdac8a24c666948e9965755e](https://private-user-images.githubusercontent.com/10821623/326407196-5646b43a-e3ff-411e-a7be-849c8db4fca8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE2MjIyNzgsIm5iZiI6MTcyMTYyMTk3OCwicGF0aCI6Ii8xMDgyMTYyMy8zMjY0MDcxOTYtNTY0NmI0M2EtZTNmZi00MTFlLWE3YmUtODQ5YzhkYjRmY2E4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzIyVDA0MTkzOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNjZTQ2MGE3ZTg0MGFjMzgxZDM0ZDkzZDg2YzAyN2I2NGI2ZGMwNjg5ODEyYzlhMmU3ZjNlN2Q0MDFmOTM5OGQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.DTfC64GpKg4n-SR9LrECdXTSET6h3ymaxmFjpHpnOqo)
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: