[Other]: How is consistent hashing implemented for sharding WebSocket connections in openim k8s? #2298
Labels
other
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Comments
hezhenke
added
the
other
|
Hello! Thank you for filing an issue. If this is a bug report, please include relevant logs to help us debug the problem. Join slack 🤖 to connect and communicate with our developers. |
skiffer-git
changed the title
|
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
|
why noboy answer the question ? |
|
A new Kubernetes deployment solution with a consistent hashing approach will be released later. It is not yet complete, but thank you for your attention. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to share?
看代码没有看懂，目前有k8s和zookeeper两种分片逻辑，k8s通过用户id哈希一致性，选定长链接节点。
我的问题是用户建立连接的时候，是在哪里让客户端根据用户ID哈希和对应的websocket服务器节点建立长链接的。
Additional information
No response
The text was updated successfully, but these errors were encountered: