You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Mickael Maison (Jira)" <ji...@apache.org> on 2023/02/08 14:54:00 UTC

[jira] [Created] (KAFKA-14692) Issues in Zookeeper to KRaft migration docs

Mickael Maison created KAFKA-14692:
--------------------------------------

             Summary: 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


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:
# 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
However if I do that, my brokers fails to restart and print:
org.apache.kafka.common.config.ConfigException: If using zookeeper.metadata.migration.enable in KRaft mode, zookeeper.connect must also be set.

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:
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) 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)