milvus: [Bug]: two proxy nodes do not load balance

Is there an existing issue for this?

I have searched the existing issues

Environment

- Milvus version: master-20211023-6949350
- Deployment mode(standalone or cluster): cluster
- SDK version(e.g. pymilvus v2.0.0rc2): rc8-dev14
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

when inserting data into several collections with multiple threads, only one of two proxy nodes is working

Expected Behavior

2 proxy node load balanced

Steps To Reproduce

1. deploy milvus clsuter with 2 proxy node
2. insert data into several collections with multiple threads

Anything else?

No response

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 15 (14 by maintainers)

Most upvoted comments

@DragonDriver Hi. I have, I suppose, similar problem. Does this grpc connection issue also affect on querynode loadbalancing? I’ve got 1 proxy and 3 querynodes but only 2 querynodes deal with requests. Of course, proxy and pulsar broker gonna give requests to querynode though, why only 2 querynodes react? Here is the picture on Grafana.

Hi Writtic, querynode load balance is probably due to other issues. You can try to release and load collection see if the problem can be solved. We’ll introduce handoff(RC8) and dynamic load balanace(GA) so once GA released the problem should be solved~ Thanks

xiaofan-luan on Nov 2, 2021