hi Colin https://github.com/apache/kafka/pull/17210 tries to revise the error message of KAFKA-17543. I guess the 3.9 RC is in progress, so could you please take a look at the PR? If it is too trivial to be included, I think it can be excluded from trunk too since 4.0 will abandon the zk.
Thanks, Chia-Ping On 2024/09/14 20:14:41 Colin McCabe wrote: > Thanks, everyone. It looks like the blockers list is empty now. I am running > some ducktape tests and if they look good, will create a release candidate > for 3.9.0 soon. > > regards, > Colin > > > On Wed, Sep 11, 2024, at 10:01, Matthias J. Sax wrote: > > Hi Colin, > > > > we found another blocker bug: > > https://issues.apache.org/jira/browse/KAFKA-17527 > > > > Working on a fix. > > > > > > -Matthias > > > > On 9/9/24 6:51 PM, David Arthur wrote: > >> Colin, > >> > >> I found a race condition in the migration while investigating a flaky test. > >> If encountered, the migration driver will get stuck initializing. > >> > >> JIRA: https://issues.apache.org/jira/browse/KAFKA-17506 > >> PR: https://github.com/apache/kafka/pull/17147 > >> > >> I wouldn't normally consider this a blocker, since it's quite rare and easy > >> to work around, but I wanted to raise it here since this is our last chance > >> for migration fixes in 3.x > >> > >> -David > >> > >> > >> > >> On Mon, Sep 9, 2024 at 3:50 AM Lucas Brutschy > >> <lbruts...@confluent.io.invalid> wrote: > >> > >>> Hi Colin, > >>> > >>> about KAFKA-17489, the bug Bruno mentioned. This needs to be fixed in > >>> 3.8 as well. The fix is probably small but tricky to get right - Bruno > >>> has attempted to fix it, but soaking revealed that the fix is not > >>> complete. Bruno is now out with Covid, so I will look into it. I'll > >>> update this thread once I know more. > >>> > >>> Cheers, > >>> Lucas > >>> > >>> On Mon, Sep 9, 2024 at 4:47 AM Colin McCabe <cmcc...@apache.org> wrote: > >>>> > >>>> Hi Chia-Ping Tsai, > >>>> > >>>> Thanks for the bug report. Let’s follow up on this this week. > >>>> > >>>> Best, > >>>> Colin > >>>> > >>>> On Fri, Sep 6, 2024, at 06:19, Chia-Ping Tsai wrote: > >>>>> hi Colin > >>>>> > >>>>> I raise a issue (https://issues.apache.org/jira/browse/KAFKA-17492) as > >>>>> 3.9 blocker, since the bug obstructs us from registering 3.9 broker to > >>>>> 3.8 controller > >>>>> > >>>>> Best, > >>>>> Chia-Ping > >>>>> > >>>>> On 2024/08/09 01:46:35 Colin McCabe wrote: > >>>>>> Hi all, > >>>>>> > >>>>>> I think it's time to transition the 3.9 branch to feature freeze. > >>> Please note that this is 2 weeks past the original planned date. I > >>> apologize for this; our planning wasn't perfect. > >>>>>> > >>>>>> A few updates on features that are in or out of Apache Kafka 3.9: > >>>>>> > >>>>>> - We have completed all the feature work for KIP-853: KRaft > >>> controller membership changes. (Please note that there are still a few bug > >>> fixes remaining, and the docs JIRA, KAFKA-17048, but those are all > >>> post-feature-freeze tasks.) > >>>>>> > >>>>>> - After speaking with Calvin, I moved KIP-966 out of 3.9 and into > >>> 4.0. I do feel bad about this but I just don't think we'll be able to get > >>> it into this short release. > >>>>>> > >>>>>> There are a few other KIPs that probably need to be moved to 4.0, > >>> such as KIP-1023 and KIP-1025. I will do a more thorough review tomorrow > >>> and reach out to people if there are gray areas. If you have a feature > >>> that > >>> you have questions about, please reach out. > >>>>>> > >>>>>> I would like to extend code freeze for Kafka 3.9 to August 29th. My > >>> reasoning is that code freeze was 2 weeks later than expected, and also, I > >>> will be out of the office most of next week. > >>>>>> > >>>>>> I have also created a PR to mark 3.9-IV0 as stable, so look for that > >>> shortly in trunk and 3.9. > >>>>>> > >>>>>> As previously mentioned, please refrain from changing the Java > >>> version in trunk (kafka 4.0) until we get an RC out. (However, please do > >>> continue working on your 4.0 features and other refactors in trunk, even > >>> if > >>> they don't apply to 3.9!) > >>>>>> > >>>>>> Thanks to everyone who has worked on this release, and thanks for > >>> your patience. I do believe we will deliver on the promise of a > >>> much-shorter-than-usual release cycle, even with the 2 week delay. > >>>>>> > >>>>>> best, > >>>>>> Colin > >>>>>> > >>> > >> > >> >
