-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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][standalone] search raises error partition not loaded
after partition loaded, and search raises error collection not loaded
after partition released in multi-partition scene
#37849
Comments
/assign @czs007 |
The problem here is not proxy cache. it's querycoord trying to add extra check on GetShardLeadersWithChannels. To me, this is check is fully unnecessary. Querycoord should just return shard delegator's location to proxy and proxy should send request to the right delegator and let delegator itself should be responsible to hold request if they are not ready. Try to think in a more succinct way of who should be responsible of doing what is very important. Right now we add too many temporary logic to fix corner cases and make the system very hard to understand. |
same root cause,different errorargo task: multi-vector-corn-1-1732197600 server:
client log:
test steps:
|
same root cause,different errorargo task:multi-vector-corn-1-1732197600 server:
client log:
test steps:
|
@czs007 @weiliu1031 please help check ~ |
Maybe the root cause is the sameargo task: fouramf-bitmap-scenes-5xlvn server:
client log:
test steps:
|
reproduceargo task: fouramf-bitmap-scenes-5xlvn server:
client log:
test steps:
|
Is there an existing issue for this?
Environment
Current Behavior
argo task: fouramf-bitmap-scenes-h5n9j/
test case name: test_bitmap_locust_dml_partitions_standalone
server:
search_failed.log
expect:
step 3: search not failed
step 6: search raises error
partition not loaded
{pod=~"fouramf-bitmap-scenes-h5n9j-6-milvus-standalone-6db4bb95cdnq5lk"} |~ "e6d76ba73466916c6d9d58288528e6e8|scene_test_partition_MmORR0U8"
Expected Behavior
No response
Steps To Reproduce
Milvus Log
No response
Anything else?
test result:
The text was updated successfully, but these errors were encountered: