mirror of https://github.com/apache/kafka.git
46d76269fa
This PR fixes a couple of things related to the #15193 PR. When you complete "Enter Migration Mode on the brokers", we are actually in "Enabling the migration on the brokers" referring to the migration guide and the broker doesn't really have node.id yet but still broker.id, so the PR removes a statement saying to replace the one with the other. Also, during rollback it's not enough just deleting the /controller znode quickly after shutting down controllers because the controller election doesn't start yet until at least one broker is rolled back with the right configuration. Until the rolling and when controllers are down, the brokers just log something like this even if you deleted the znode "quickly": [2024-01-30 09:27:52,394] DEBUG [zk-broker-0-to-controller-quorum-channel-manager]: Controller isn't cached, looking for local metadata changes (kafka.server.BrokerToControllerRequestThread) [2024-01-30 09:27:52,394] INFO [zk-broker-0-to-controller-quorum-channel-manager]: Recorded new controller, from now on will use node localhost:9093 (id: 1 rack: null) (kafka.server.BrokerToControllerRequestThread) You have to reduce the amount of time between deleting the znode and rolling at least one broker, so that an election can start. Reviewers: Luke Chen <showuon@gmail.com> |
||
|---|---|---|
| .. | ||
| documentation | ||
| images | ||
| js | ||
| streams | ||
| api.html | ||
| configuration.html | ||
| connect.html | ||
| design.html | ||
| docker.html | ||
| documentation.html | ||
| ecosystem.html | ||
| implementation.html | ||
| introduction.html | ||
| migration.html | ||
| ops.html | ||
| protocol.html | ||
| quickstart.html | ||
| security.html | ||
| toc.html | ||
| upgrade.html | ||
| uses.html | ||