Hello, I would like to report a bug in KRaft.
Dynamic broker configs are not being validated on the brokers before being forwarded to the controller and persisted in the metadata quorum. This is a blocker because a core requirement of KRaft mode in 3.0 is that it should support upgrades from 3.0. If invalid dynamic configs are persisted to metadata then they will still be there after an upgrade. I believe that this should be considered as a blocker for 3.0 here is the JIRA: https://issues.apache.org/jira/browse/KAFKA-13142. I will be working on a PR this week. Best Regards, Ryan On Wed, May 26, 2021 at 2:48 PM Konstantine Karantasis <konstant...@confluent.io.invalid> wrote: > Hi all, > > Please find below the updated release plan for the Apache Kafka 3.0.0 > release. > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177046466 > > New suggested dates for the release are as follows: > > KIP Freeze is 09 June 2021 (same date as in the initial plan) > Feature Freeze is 30 June 2021 (new date, extended by two weeks) > Code Freeze is 14 July 2021 (new date, extended by two weeks) > > At least two weeks of stabilization will follow Code Freeze. > > The release plan is up to date and currently includes all the approved KIPs > that are targeting 3.0.0. > > Please let me know if you have any objections with the recent extension of > Feature Freeze and Code Freeze or any other concerns. > > Regards, > Konstantine >
