[
https://issues.apache.org/jira/browse/KAFKA-19228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Wu resolved KAFKA-19228.
------------------------------
Resolution: Won't Fix
Closing with won't fix, since although the current behavior is undesirable UX,
this fix would be a breaking change.
Since verifying that setting `–feature=kraft.version=X` alongside any of
`–standalone, --initial-controllers, --no-initial-controllers` does not write
anything to `bootstrap.checkpoint` or the `0-0.checkpoint` files, the current
behavior is consistent (i.e. the metadata log is always formatted correctly.
> `kafka-storage format` should not support explicitly setting kraft.version
> feature level
> ----------------------------------------------------------------------------------------
>
> Key: KAFKA-19228
> URL: https://issues.apache.org/jira/browse/KAFKA-19228
> Project: Kafka
> Issue Type: Bug
> Reporter: Kevin Wu
> Assignee: Kevin Wu
> Priority: Major
>
> When formatting, explicitly setting the kraft.version feature level with
> --feature kraft.version=X should not be supported. Instead, this feature's
> level should be inferred from the presence/absence of the following flags:
> --standalone, --initial-controllers, --no-initial-controllers.
> * When --standalone or --initial-controllers is specified, this node is
> using kraft.version=1, and will write a bootstrap snapshot with the KRaft
> version and voter set control records.
> * When --no-initial-controllers is specified, the feature level will end up
> unset because it is not used to write the bootstrap snapshot like with
> --initial-controllers and --standalone. Instead, the node will default to
> kraft.version 0 and potentially discover a higher feature level by fetching
> the log.
> * If none of these flags are specified, the static config
> controller.quorum.voters must be defined.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
