Kafka - 控制器代理
Kafka - Controller Broker
我从 https://niqdev.github.io/devops/kafka/ 看到这个短语
和 https://livebook.manning.com/book/kafka-streams-in-action/chapter-2/109（Kafka Streams 实战）
The controller broker is responsible for setting up leader/follower relationships for all partitions of a topic. If a Kafka node dies or is unresponsive (to ZooKeeper heartbeats), all of its assigned partitions (both leader and follower) are reassigned by the controller broker.
我认为将跟随者分区分配给其他代理是不正确的 - 因为除非代理回来，否则分区不会自行修复。我知道这只发生在领导者副本上，如果领导者副本的经纪人出现故障，则包含追随者的经纪人之一将成为领导者。但是，我不认为关注者的“重新分配”会自动发生，除非重新分配是手动启动的。请添加您的意见
该术语可能确实有点偏离，但仍然适用。 Followers 不一定分配给其他 broker，但他们需要将端点更改为他们要发送获取请求的位置。 The follower's job is to stay in-sync with the leader, and if the leader has been assigned to a new broker because the old one failed then the followers need to send their fetch requests to the new elected broker.我认为这就是重新分配在您分享的上下文中的含义。
我从 https://niqdev.github.io/devops/kafka/ 看到这个短语 和 https://livebook.manning.com/book/kafka-streams-in-action/chapter-2/109（Kafka Streams 实战）
The controller broker is responsible for setting up leader/follower relationships for all partitions of a topic. If a Kafka node dies or is unresponsive (to ZooKeeper heartbeats), all of its assigned partitions (both leader and follower) are reassigned by the controller broker.
我认为将跟随者分区分配给其他代理是不正确的 - 因为除非代理回来，否则分区不会自行修复。我知道这只发生在领导者副本上，如果领导者副本的经纪人出现故障，则包含追随者的经纪人之一将成为领导者。但是，我不认为关注者的“重新分配”会自动发生，除非重新分配是手动启动的。请添加您的意见
该术语可能确实有点偏离，但仍然适用。 Followers 不一定分配给其他 broker，但他们需要将端点更改为他们要发送获取请求的位置。 The follower's job is to stay in-sync with the leader, and if the leader has been assigned to a new broker because the old one failed then the followers need to send their fetch requests to the new elected broker.我认为这就是重新分配在您分享的上下文中的含义。