Hi Chia-Ping, I think the two topics are actually related as the KIP seemed to gain no attention due to the assumption that there would be no further 3.9 releases. Now that one is being planned, let's please consider if we can include a fix for the underlying issue.
Thanks, Anton Den mån 26 okt. 2026 kl 17:18 skrev Chia-Ping Tsai <[email protected]>: > Hi Tommi > > I haven’t dug into the KIP yet. As it’s a KIP, it needs to pass the > vote before the PR can be merged. > > If the KIP passes the vote, we can definitely include it in 3.9.3 :) > > BTW, this thread is for discussing whether we should make the next > release for the 3.9 branch, so let’s keep the KIP discussion on its > own thread. > > Thanks, > Chia-Ping > > Tommi Vainikainen via dev <[email protected]> 於 2026年10月26日週一 下午9:45寫道： > > > > Hi, > > > > I fully support your efforts regarding 3.9.3 release. > > > > Do you think that > > > https://cwiki.apache.org/confluence/spaces/KAFKA/pages/440303727/KIP-1362+Add+a+rollback-compatible+storage+format+option+for+KRaft+migration > > > > could be something to include in 3.9.3? It seems to be stuck in the KIP > > phase, so the pull request is also stuck. > > > > On Sun, Oct 25, 2026 at 3:19 PM Chia-Ping Tsai <[email protected]> > wrote: > > > > > Hi all, > > > > > > There are some critical bugs related to ZK migration, so I’d like to > > > open a discussion for the 3.9.3 release. > > > > > > KAFKA-20960: Block ZK-to-KRaft migration finalization until brokers > > > re-register (merged) > > > > > > > https://github.com/apache/kafka/commit/ea11d59ecda2ec57be0f1ef83a554ef5d3b82770 > > > > > > KAFKA-21142: Fix partition creation when handling snapshot delta > > > during migration (merged) > > > > > > > https://github.com/apache/kafka/commit/daebfbd9b37c913937d5adfc2e493fe825e3da3a > > > > > > KAFKA-21062: Handle BADVERSION on /migration writes (under review) > > > https://github.com/apache/kafka/pull/23639 > > > > > > My sense is that ZK migration is the only official way to encourage > > > users to get into KRaft, so keeping it working is a strong reason to > > > do a release. > > > > > > I haven’t finished reviewing the last one yet, but it would be good to > > > make sure the release will happen. Otherwise, my tokens will be > > > totally wasted :) > > > > > > Any thoughts? > > > >
