Hi Alyssa, thanks for the feedback. See my comments below. On Wed, Aug 27, 2025 at 6:13 PM Alyssa Huang <ahu...@confluent.io.invalid> wrote: > This is the expected state for a cluster which upgraded from pre-KIP-1170 > to post-KIP-1170?
Correct. It upgraded software version before a controller became active, committed the bootstrap records and generated a new snapshot. > And this would be the expected state on startup for newly provisioned > clusters that implement KIP-1170? Correct. > Can we explain why this should not be possible? It might not be obvious to > readers Because the kafka-storage tool cannot generate this state. The format command for the storage tool will either store the initial metadata record in the bootstrap.checkpoint or the zero checkpoint but not both. > Also, what do you think about breaking the Proposed Changes section into > two examples? How new changes impact newly provisioned clusters vs existing > clusters (with bootstrap.checkpoint). Okay. > For instance, it seems I should interpret the above scenario as when the > cluster existed pre-KIP-1170, but it's possible for the controller not to > load a snapshot at epoch 0 and offset 0 solely because that snapshot was > deleted due to retention. That's one possibility. The other possibility is that the zero checkpoint was never created. This is possible if it is a cluster that was upgraded to a version that supports this feature. Thanks! -- -José
