openimsdk
OpenIM3's highly available components are best selected with etcd/zookeeper rather than fixed as zookeeper，again。
Checklist
- [X] I've searched for similar issues and couldn't find anything matching
- [X] I've discussed this feature request in the OpenIMSDK Slack and got positive feedback
Is this feature request related to a problem?
None
Problem Description
OpenIM3's highly available components are best selected with etcd/zookeeper rather than fixed as zookeeper, so that the use can be selected. The use of Go-based etcd seems to be more in line with the OpenIM project developed in the Go language, and ETCD is far more active than Zookeeper.
Solution Description
OpenIM3's highly available components are best selected with etcd/zookeeper rather than fixed as zookeeper, so that the use can be selected.
Benefits
The use of Go-based etcd seems to be more in line with the OpenIM project developed in the Go language, and ETCD is far more active than Zookeeper.
Potential Drawbacks
No response
Additional Information
No response
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.
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.
This issue was closed because it has been stalled for 7 days with no activity.
In which version of the project does zookeeper drop, use etcd? etcd is more active, it is basically the basic component of the system, and the maximum benefit can be obtained from using etcd.
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.
this issue has fixed in release-v3.8, I recommend you update to new version. If you run into any new issues, please reopen this issue or create a new one.
