[Bug]: it takes 12s to return 'count(*)' query for an unloaded , empty collection

[shanghaikid]

Is there an existing issue for this?

• I have searched the existing issues

Environment

- Milvus version: v2.4.14 & master

Current Behavior

it takes 12s to finish the query, which freezes the attu every time when loading the collection info.

2024-11-08T05:25:07.934Z] Milvus-sdk-node debug: [Request]v054ps.....>default>Query(15s): {"collection_name":"t","expr":"","output_fields":["count(*)"],"db_name":"default","query_params":[]}
[2024-11-08T05:25:19.963Z] Milvus-sdk-node debug: [Response(12029ms)]v054ps.....>default>Query: {"fields_data":[],"output_fields":[],"status":{"extra_info":{},"error_code":"UnexpectedError","reason":"failed to query: collection not loaded[collection=453759196215302711]","code":101,"retriable":false,"detail":"failed to query: collection not loaded[collection=453759196215302711]"},"collection_name":""}

Expected Behavior

it should return collection not loaded error right away.

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

[yanliang567]

/assign @bigsheeper
/unassign

[bigsheeper]

Quick question: Does the 12s include the time for quick setup (which including CreateCollection and CreateIndex)? @shanghaikid

[shanghaikid]

Quick question: Does the 12s include the time for quick setup (which including CreateCollection and CreateIndex)? @shanghaikid

no, just query.

[xiaofan-luan]

UnexpectedError

UnexpectedError ->
I guess the error code is hacked somewhere, cause retry some where.

And the timeout is not set for some reason, cause the retry take for ever.

@bigsheeper we need to fix the error code and make sure the retry follow timeout

[shanghaikid]

@xiaofan-luan I believe this fix should also be applied to version 2.4.x. Otherwise, users of Attu with that version will face significant slowness.

[czs007]

@shanghaikid please help verify

[shanghaikid]

verified on master-20241114-1d06d432-amd64