[KAFKA-14697] KRaft controller should not send LISR to KRaft brokers during migration

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.4.0
• Component/s: kraft
• Assignee: Unassigned
• Reporter: David Arthur
• Created: 09/Feb/23 15:20
• Updated: 09/Feb/23 15:48
• Resolved: 09/Feb/23 15:47

Description

During a migration, after a broker is restarted in KRaft mode the KRaft controller is still sending it LISR as if it were a ZK broker. This results in errors like:

[2023-02-09 14:53:26,892] ERROR Closing socket for 172.19.0.4:9092-172.19.0.9:32876-0 because of error (kafka.network.Processor)
org.apache.kafka.common.errors.InvalidRequestException: Received request api key LEADER_AND_ISR which is not enabled

This can be observed by running the kafkatest.tests.core.zookeeper_migration_test.TestMigration.test_online_migration ducktape test. Attached are logs from a local run of this test with --debug set.

It seems these errors do not affect the consistency of metadata during the migration, but the excessive LISR sent out will impact performance on large clusters.

Issue Links

• duplicates: KAFKA-14698 Received request api key LEADER_AND_ISR which is not enabled