-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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]: Getting error "index not supported" for GPU CAGRA index, please help #34220
Comments
/assign @Presburger |
@yanliang567 @Presburger is there another milvus version/release that successfully works with GPU_CAGRA? I think this is a regression seeing another ticket for DiskANN: #34222, We are ok to test with any version as long as it works |
@kdabbir I think you didn't enable GPU when building the image; by default, it's a CPU image. Please check it. |
@kdabbir Hi, could you provide more detailed log information? |
All I did is
Sure, let me take an export of logs and attach |
milvus-log.tar.gz |
logs taken from above zip in proxy and data coord:
|
I got it working, the documentation needs to be updated, basically I had to add below config:
gpu - enable:true is needed to enable GPU i believe, please update this documentation to add this configuration: https://milvus.io/docs/index-with-gpu.md#Configure-Milvus-settings-for-GPU-memory-control |
GPU&CPU are two different images since GPU will bring many extra dependencies. |
@kdabbir Hello, under the |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there an existing issue for this?
Environment
Current Behavior
Explained the issue here in discord: https://discord.com/channels/1160323594396635310/1255592726355775518
Posting a bug here so that we can get quick help to resolve this. Would appreciate quick insights to fix this as we plan to complete GPU Cagra benchmarking and testing ASAP
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: