scholzj commented on code in PR #14484:
URL: https://github.com/apache/kafka/pull/14484#discussion_r1347332138
##########
docs/upgrade.html:
##########
@@ -144,8 +144,10 @@ <h5><a id="upgrade_350_kraft"
href="#upgrade_350_kraft">Upgrading KRaft-based cl
./bin/kafka-features.sh upgrade --metadata 3.5
</code>
</li>
- <li>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.</li>
+ <li>Note that cluster metadata downgrade is not supported, although it
might be possible to do a safe downgrade in some cases.
Review Comment:
What are the cases the downgrade is supported after you do the
`./bin/kafka-features.sh upgrade --metadata 3.5` step that directly precedes
this? I think this should be worded much more strongly.
```suggestion
<li>Once you upgrade the metadata version to `3.5`, there is no
possibility of downgrade.
```
And I think the same applies to 3.4 and likely also for 3.3 (I did not
checked that one in detail).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
