You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Federico Valeri (Jira)" <ji...@apache.org> on 2023/10/04 12:25:00 UTC
[jira] [Updated] (KAFKA-15537) Unsafe metadata.version downgrade is not supported
[ 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" downgrade functionality in case one of the metadata versions between current and target have changes, 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}
was:
In KIP-778 we introduced the "unsafe" downgrade functionality in case one of the metadata versions between current and target have changes, as defined in MetadataVersion. This is a lossy downgrade where each node rebuilds its metadata snapshots, omitting the new metadata fields. 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}
> Unsafe metadata.version downgrade is not supported
> --------------------------------------------------
>
> Key: KAFKA-15537
> URL: https://issues.apache.org/jira/browse/KAFKA-15537
> Project: Kafka
> Issue Type: Bug
> Reporter: Federico Valeri
> Priority: Major
>
> In KIP-778 we introduced the "unsafe" downgrade functionality in case one of the metadata versions between current and target have changes, 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}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)