[
https://issues.apache.org/jira/browse/KAFKA-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Valeri updated KAFKA-15537:
------------------------------------
Affects Version/s: 3.6.0
(was: 3.5.1)
> Unsafe metadata.version downgrade is not supported
> --------------------------------------------------
>
> Key: KAFKA-15537
> URL: https://issues.apache.org/jira/browse/KAFKA-15537
> Project: Kafka
> Issue Type: Bug
> Components: documentation
> Affects Versions: 3.6.0
> Reporter: Federico Valeri
> Assignee: Federico Valeri
> Priority: Major
> Fix For: 3.7.0, 3.6.1
>
>
> In KIP-778 we introduced the "unsafe" (lossy) downgrade in case metadata has
> changes in one of the versions between target and current, as defined in
> MetadataVersion.
> The documentation says it is possible.
> bq. Note that the cluster metadata version cannot be downgraded to a
> pre-production 3.0.x, 3.1.x, or 3.2.x version once it has been upgraded.
> However, it is possible to downgrade to production versions such as 3.3-IV0,
> 3.3-IV1, etc.
> The command line tool shows that this doesn't work.
> {code}
> bin/kafka-features.sh --bootstrap-server :9092 downgrade --metadata 3.4
> --unsafe
> Could not downgrade metadata.version to 8. Invalid metadata.version 8. Unsafe
> metadata downgrade is not supported in this version.
> 1 out of 1 operation(s) failed.
> {code}
> This is also a mentioned in KIP-868: "Note that lossy downgrades of the
> metadata log are detailed in KIP-778 and not yet fully implemented as of
> Kafka 3.3".
> Additionally, you can't do any safe downgrade, because cluster metadata
> records are still evolving and every release has changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
