Hi all, Thanks for the comments. I agree that we should split out declaring KRaft going production for new clusters from deprecating ZK. We can do the former in the next release, 3.3, and the latter in the release after that, 3.4.
I also talked offline with some of the people working on upgrade from ZK and it seems like 3.4 is a more realistic target for that work. Partly this is because 3.3 will be a bit earlier than I originally thought (for some reason I thought it might be October, but Ismael pointed out it's planned for August) I also agree that it will probably be useful to have a 3.5 release following the 3.4 one, which will also support ZK. Hopefully we will not need a 3.6, but we don't have to decide that now. I added a timeline section to the KIP to make this all clearer. To be clear, it is a preliminary timeline, which may change. It's difficult to fully plan out the next 1.5 years of Apache Kafka releases right now -- and obviously, there are things which may come up to change our plans. However, I think it is still helpful to have the section to give us a feeling for the general roadmap. When you read the KIP, please consider it all speculative except for the three proposed changes at the top: 1. Mark KRaft as production-ready for new clusters in the upcoming Kafka 3.3 release. 2. Deprecate ZooKeeper mode in the upcoming Kafka 3.4 release 3. Plan to remove ZooKeeper mode entirely in Kafka 4.0. best, Colin On Wed, May 4, 2022, at 19:31, Ismael Juma wrote: > Yes, all features supported by zk mode will be available in kraft mode in > the 3.x series. > > Ismael > > On Wed, May 4, 2022, 5:28 PM Israel Ekpo <israele...@gmail.com> wrote: > >> Ismael, >> >> I like the timeline. However, does this or will this also account for >> features users rely on today in Zookeeper mode being available when >> Zookeeper is dropped? >> >> That’s my main concern >> >> On Wed, May 4, 2022 at 8:12 PM Ismael Juma <ism...@juma.me.uk> wrote: >> >> > Hi Colin, >> > >> > Thanks for the KIP, this is exciting. Trying to balance progress and >> > compatibility, how about the following? >> > >> > 1. 3.3 (~August 2022): kraft is production ready for new clusters >> > 2. 3.4 (~December 2022/January 2023): migration from zk to kraft is >> > production ready and zk mode is deprecated >> > 3. 3.5 (~April 2023): buffer release >> > 4. 4.0 (~August 2023): kraft mode is on by default and zk mode is removed >> > >> > This would mean about 1 year from kraft being production ready to zk >> > removal and 8 months from zk deprecation to zk removal. >> > >> > If necessary (due to important bugs or security issues), we can do a >> couple >> > of additional bug fix releases in the 3.5 series after 4.0 is released. >> > >> > Thoughts? >> > >> > Ismael >> > >> > On Tue, May 3, 2022, 6:03 PM Colin McCabe <cmcc...@apache.org> wrote: >> > >> > > Hi all, >> > > >> > > I've written a KIP for marking KRaft as production ready. Please take a >> > > look if you have a chance: >> > > >> > > https://cwiki.apache.org/confluence/x/8xKhD >> > > >> > > thanks, >> > > Colin >> > > >> > >> -- >> Israel Ekpo >> Lead Instructor, IzzyAcademy.com >> https://www.youtube.com/c/izzyacademy >> https://izzyacademy.com/ >>
