-
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]: [benchmark] milvus panic SIGSEGV: segmentation violation
when enabled queryNode.segcore.multipleChunkedEnable
#36834
Comments
/assign @sunby let's enable this feature by default so we can find more bug |
yes, we plan to enable this after some stability tests |
I will build a debug image and try to reproduce it. |
Fix segmentation fault error and remove useless codes. #36834 Signed-off-by: sunby <sunbingyi1992@gmail.com>
sorry, I made a stupid mistake. fixed in #37064 |
issue: #36834 Signed-off-by: sunby <sunbingyi1992@gmail.com>
@wangting0128 |
Verification passed, milvus not panic, but raises new error: |
Is there an existing issue for this?
Environment
Current Behavior
argo task: fouramf-concurrent-kd529
test case name: test_bitmap_locust_dql_dml_standalone
server:
fouram-54-5077-milvus-standalone-7d64cf9cf6-ftfbs-panic.log
Expected Behavior
No response
Steps To Reproduce
Milvus Log
No response
Anything else?
server config:
client config:
The text was updated successfully, but these errors were encountered: