-
Notifications
You must be signed in to change notification settings - Fork 165
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
milvus集群版search压力倾斜 #911
Comments
是否是因为索引建不过来,数据都在delegator上,无法balance?可以使用birdwatcher看看。 |
我部署的是2.2版本,只有一个proxy的cpu水位上涨,而且一直是同一个。我开了两个java服务去压测,有两个proxy的cpu水位上涨。sdk是有长链接吗? |
sdk的连接基本上是长连接,proxy如果有多个,那它们的地址都是不同的。客户端连接不同的proxy就应该连接不同的proxy地址。如果只有一个proxy在忙,那说明你的客户端全都连的同一个proxy。milvus本身并没有proxy的balance机制。 |
如果是proxy,你需要在proxy之前加负载均衡。 |
我部署了milvus集群版,一共5个node。
启动了一个java服务使用sdk压测milvus的search,但是只有一个node的cpu水位大幅上涨,其他node变化不大。
这是为什么?
The text was updated successfully, but these errors were encountered: