[
https://issues.apache.org/jira/browse/KAFKA-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Valeri updated KAFKA-15537:
------------------------------------
Description:
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}
In addition to unsafe, also safe metadata downgrades are not supported in
practice. For example, when you upgrade to 3.5, you land on 3.5-IV2 as metadata
version, which has metadata changes and won't let you to downgrade. This is
true for every other release at the moment.
was:
In KIP-778 we introduced the "unsafe" downgrade in case metadata has changes in
one of the versions between target and current, as defined in MetadataVersion.
This is a lossy downgrade where each node rebuilds its metadata snapshots,
omitting the metadata changes.
Currently, this is not supported, as shown by the following command.
{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}
The documentation says it is possible:
"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."
In addition to unsafe, also safe metadata downgrades are not supported in
practice. When you upgrade to 3.5, you land on 3.5-IV2 as metadata version,
which has metadata changes and won't let you to downgrade. This is true for
every other release at the moment.
> 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.5.1
> 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}
> In addition to unsafe, also safe metadata downgrades are not supported in
> practice. For example, when you upgrade to 3.5, you land on 3.5-IV2 as
> metadata version, which has metadata changes and won't let you to downgrade.
> This is true for every other release at the moment.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
