...
As we only upgraded the rebalance metadata in 0.10.1.0, there is no RocksDB upgrade required and a single upgrade mode is sufficient for this case and thus parameter upgrade.mode
is no required. Note, that there would be an dependency between upgrade.from
and upgrade.mode
: If we include the fix for KAFKA-6054 and also back port the fix to order version, the upgrade.from
parameter would be the "main" parameter enabling upgrade behavior. For this case, it's required to set upgrade.mode
, too (if available). If upgrade.from
is not set, the value of upgrade.mode
is ignored and does not have any effect. If we don't include a fix for KAFKA-6054 there will be only one parameter upgrade.mode
though – the upgrade steps below are targeted for this case.
Upgrade from | Upgrade to | Set config upgrade. | modefrom to | Set config
| Side remark |
---|---|---|---|---|---|
0.10.0.x | 0.10.1.x, ..., 1.1.x | N/A | "0.10.0.x" | N/A | fixed KAFKA-6054 for releases 0.10.1.x, ..., 1.1.x |
0.10.0.x | 1.2 | "0.10.0.x" |
| ""0.10.0.x
| fixed KAFKA-6054 for 1.2 release |
0.10.1.x, ..., 1.1.x | 1.2 | " | in_place"or "0.10.1.x-1.1.x" | "in_place" or "roll_over" |
Details about the different behavior for all types of upgrades are given below.
...