You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 32d7f0f
Browse filesBrowse the repository at this point in the historyBrowse files
fix(backups): restore Kafka 3.x topic configs that Kafka 4 rejects
Every Kafka now runs 4.x, and a topic-metadata backup taken on Kafka
3.8 or 3.9 can record message.format.version,
message.downconversion.enable or message.timestamp.difference.max.ms,
which Kafka 4 removed, or a segment.bytes below 1 MiB, the minimum
Kafka 4 raised it to from 14 bytes. A 4.x broker rejects each of them,
so the restore stopped at the first one, leaving that topic
half-configured and every later topic unrestored, and a rerun failed
on the same line.
The restore now skips the removed keys and raises a smaller
segment.bytes to the minimum, each with a warning, and applies the
rest.
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <[email protected]>
# Kafka 4 raised the segment.bytes floor to 1 MiB.
116
+
case "\$add" in
117
+
segment.bytes=*)
118
+
[ "\${add#*=}" -ge 1048576 ] || { echo "InvalidConfigurationException: Invalid value \${add#*=} for configuration segment.bytes: Value must be at least 1048576" >&2; exit 1; } ;;
0 commit comments