tomsun28 commented on issue #3221: URL: https://github.com/apache/hertzbeat/issues/3221#issuecomment-2816507015
hi👍 This is just my initial idea. I will conduct in-depth research on it when have time. We can see some manager data are stateful data, eg: the consisten hash ring, cluster state info. These stateful data need be maintan by Leader and the Followers synchronously copy this data from the Leader to ultimately maintain data consistency. The Leader down, the Follower one of them become the new Leader. > How do collectors initially connect — do they always connect directly to the leader, or to any manager and get redirected? I think the collectors can connect anyone of the managers, due the `consisten hash ring` state is same in all manager. Maybe here we can learn from kafka-client brokers cluster to see how them design. > How are collection jobs assigned and pushed to collectors? As above, The Leader decides the jobs assigned and collectors, the followers sync copy data from Leader, and then implement the actual allocation. But here we still need to consider, if the collector registers any manager, how does the leader know which collector has registered? > How is metric data returned and handled in this model? Maybe it will be the same as now(the collector send the data to connected manager directly), but we need to consider unified data processing and unified alarm calculation -- 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]
