Open cubxxw opened 11 months ago
Native to Kafka: Simplifies Kafka setup and reduces external dependencies. Improved stability and fewer moving parts.
It is recommended to use the native kafka, fewer components means more robust.
It is also good to be able to reuse Kafka's kraft mechanism, since Kafka can use kraft, the consistency mechanism should be reliable. The main thing is whether it meets the consistency and performance requirements of OpenIM.
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.
/restart
请问可以提供一个去掉zookeeper的选项吗?
Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿
Can you please provide an option to remove zookeeper?
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.
@fuyuku
请问可以提供一个去掉zookeeper的选项吗?
We are implementing this part of the logic, which is necessary
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.
We have recently upgraded to Kafka version 3.5.1 in our Docker Compose setup. Notably, recent versions of Kafka no longer have a dependency on Zookeeper. However, our current Docker Compose file still contains configurations for Zookeeper.
Given this change, we should consider replacing Zookeeper to modernize our Kafka setup and possibly reduce resource overhead. One known alternative is Kraft. However, we are open to suggestions on other alternatives.
Requirements:
Potential Alternatives:
table:
Action items: