Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
3.4.0
-
None
-
None
Description
I started from a Kafka cluster (with ZooKeeper) with 2 brokers. There's a single topic "test" with 2 partitions and 2 replicas and the internal __consumer_offsets topics.
While following the ZooKeeper to KRaft migration steps from https://kafka.apache.org/documentation/#kraft_zk_migration, I'm hitting issues at the Migrating brokers to KRaft step.
When I restart a broker as KRaft, it repetitively prints the following error:
org.apache.kafka.common.errors.InvalidRequestException: Received request api key LEADER_AND_ISR which is not enabled
[2023-02-09 16:14:30,334] ERROR Closing socket for 192.168.1.11:9092-192.168.1.11:63737-371 because of error (kafka.network.Processor)
The controller repetitively prints the following error:
[2023-02-09 16:12:27,456] WARN [Controller id=1000, targetBrokerId=0] Connection to node 0 (mmaison-mac.home/192.168.1.11:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient) [2023-02-09 16:12:27,456] INFO [Controller id=1000, targetBrokerId=0] Client requested connection close from node 0 (org.apache.kafka.clients.NetworkClient) [2023-02-09 16:12:27,560] INFO [Controller id=1000, targetBrokerId=0] Node 0 disconnected. (org.apache.kafka.clients.NetworkClient)
Attached the controller logs and logs from broker-0
Attachments
Attachments
Issue Links
- duplicates
-
KAFKA-14918 KRaft controller sending ZK controller RPCs to KRaft brokers
- Resolved
- is duplicated by
-
KAFKA-14697 KRaft controller should not send LISR to KRaft brokers during migration
- Resolved
- relates to
-
KAFKA-14304 ZooKeeper to KRaft Migration
- Resolved