- Milvus version:master and 2.4
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
Current Behavior
proxy will update shard leader cache first, then release the lock and try to init shard client. which cause a period that user can get shard leader from meta cache, but can't find shard client from shard client manager
Is there an existing issue for this?
Environment
Current Behavior
proxy will update shard leader cache first, then release the lock and try to init shard client. which cause a period that user can get shard leader from meta cache, but can't find shard client from shard client manager
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response