tomsun28 commented on issue #3221: URL: https://github.com/apache/hertzbeat/issues/3221#issuecomment-2809980574
hi very detailed and carefully designed. 👍 I have some questions about this. The Shared Storage is a program or the `redis` to control the collector hearbeat and hash-cyclic dispatch ? Seem if we want to achieve distributed multi-managers and high availability, it seems that we need a highly available cluster of Kafka and a highly available redis cluster to build this. I personally feel that the architecture is too complicated, which makes it difficult for users to maintain. Multiple external dependencies also expose more potential points of failure. How about we just use the multi-managers? use the raft protocol to implement one-leader-manager, multi-follower-managers strument. - Regarding the consistent hash ring state, we can let the followers synchronize the data of the primary leader. - The collector will connect to any one manager, but they will periodically synchronize metadata information to know who the current leader manager is. - The leader controls the changes to public data, and other nodes only follow and replicate. - When the leader goes down, the Raft protocol elects a new leader node and continues, and also notifies the collector. - We also need to modify the manager to keep other data as stateless as possible. - so on This is just my simple idea. Maybe there are better solutions. Welcome to discuss. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
