[
https://issues.apache.org/jira/browse/KAFKA-14692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686352#comment-17686352
]
Luke Chen commented on KAFKA-14692:
-----------------------------------
I was wrong about the workaround. It just let the broker doesn't get the
Leader_And_Isr request due to listener change. So, we still need to find out
the root cause. It looks like we should not use KRaftMigrationDriver to publish
events if the broker is completely migrated to KRaft mode.
> Issues in Zookeeper to KRaft migration docs
> -------------------------------------------
>
> Key: KAFKA-14692
> URL: https://issues.apache.org/jira/browse/KAFKA-14692
> Project: Kafka
> Issue Type: Improvement
> Components: docs
> Reporter: Mickael Maison
> Assignee: David Arthur
> Priority: Major
>
> Following [https://kafka.apache.org/documentation/#kraft_zk_migration]
> 1) It completely skips the facts that the storage for the new quorum should
> be formatted using the existing cluster id.
> 2) In Provisioning the KRaft controller quorum:
> {{controller.quorum.voters=1@localhost:9093}} should be
> {{controller.quorum.voters=3000@localhost:9093}} as node.id=3000
> 3) When migrating brokers, it states:
> {code:java}
> # Don't set the IBP, KRaft uses "metadata.version" feature flag
> # inter.broker.protocol.version=3.4
> # Keep the migration enabled
> zookeeper.metadata.migration.enable=true
> # Remove ZooKeeper client configuration
> # zookeeper.connect=localhost:2181
> {code}
> However if I do that, my brokers fails to restart and print:
> {code:java}
> org.apache.kafka.common.config.ConfigException: If using
> zookeeper.metadata.migration.enable in KRaft mode, zookeeper.connect must
> also be set.
> {code}
> 4) When disabling zookeeper.metadata.migration.enable or keeping
> zookeeper.connect to get past this step, when brokers restart they print a
> lot of error messages:
> {code:java}
> org.apache.kafka.common.errors.InvalidRequestException: Received request api
> key LEADER_AND_ISR which is not enabled
> [2023-02-08 12:06:25,776] ERROR Exception while processing request from
> 192.168.1.11:9092-192.168.1.11:57210-107 (kafka.network.Processor)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
