[
https://issues.apache.org/jira/browse/KAFKA-18147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alyssa Huang updated KAFKA-18147:
---------------------------------
Description: Using the `config/kraft/controller.properties` packaged along
with `kafka_2.13-3.9.0`, running `bin/kafka-storage.sh format standalone -t
$KAFKA_CLUSTER_ID -c config/kraft/controller.properties` and then
kafka-features.sh describe shows that the quorum is using kraft version 0. Same
happens when bringing up a controller with `-no-initial-controllers`. However,
it is somehow possible to dynamically add that controller to the quorum despite
the advertised kraft version. (was: Using the
`config/kraft/controller.properties` packaged along with `kafka_2.13-3.9.0`,
running `bin/kafka-storage.sh format -standalone -t $KAFKA_CLUSTER_ID -c
config/kraft/controller.properties` and then kafka-features.sh describe shows
that the quorum is using kraft version 0. Same happens when bringing up a
controller with `--no-initial-controllers`. However, it is somehow possible to
dynamically add that controller to the quorum despite the advertised kraft
version.)
> kraft version of standalone KIP-853. controller should be 1 not 0
> -----------------------------------------------------------------
>
> Key: KAFKA-18147
> URL: https://issues.apache.org/jira/browse/KAFKA-18147
> Project: Kafka
> Issue Type: Bug
> Reporter: Colin McCabe
> Priority: Major
> Fix For: 3.9.1
>
>
> Using the `config/kraft/controller.properties` packaged along with
> `kafka_2.13-3.9.0`, running `bin/kafka-storage.sh format standalone -t
> $KAFKA_CLUSTER_ID -c config/kraft/controller.properties` and then
> kafka-features.sh describe shows that the quorum is using kraft version 0.
> Same happens when bringing up a controller with `-no-initial-controllers`.
> However, it is somehow possible to dynamically add that controller to the
> quorum despite the advertised kraft version.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)