Sorry but I have to vote -1 I tried verifying that the migration quotas bug described in https://issues.apache.org/jira/browse/KAFKA-16222 was fixed, and it appears to still be an issue with 3.6.2 RC1. The quota on the default resource is still getting translated improperly.
I am looking into what the issue is here. best, Colin On Thu, Mar 21, 2024, at 19:32, Chia-Ping Tsai wrote: > hi Manikumar > >> Pls let me know after merging the PR. I will generate RC2 later today. > > Sure. We will complete it ASAP > > >> Manikumar <manikumar.re...@gmail.com> 於 2024年3月22日 上午9:26 寫道： >> >> Hi, >> >> Thanks. Since we have merged KAFKA-16342 >> <https://issues.apache.org/jira/browse/KAFKA-16342>, it's probably better >> to take the PR for KAFKA-16341 >> <https://issues.apache.org/jira/browse/KAFKA-16341> for consistency. >> I am canceling the RC1 in favour of including KAFKA-16341 >> <https://issues.apache.org/jira/browse/KAFKA-16341>. >> >> Chia-Ping, >> >> Pls let me know after merging the PR. I will generate RC2 later today. >> >> >> Thank you, >> >> >> >> >> >> >> On Thu, Mar 21, 2024 at 9:10 PM Chia-Ping Tsai <chia7...@gmail.com> wrote: >> >>>> Is this a regression from the 3.5.0 release? >>> >>> I believe the bug is existent for a while, but it is not a true issue until >>> we allowed users to fetch offset of max timestamp. >>> >>>> Can we update the "Affects Version/s" field on JIRA? >>> >>> done. I attach the tags for active branches - 3.6.1 and 3.7.0 >>> >>> Manikumar <manikumar.re...@gmail.com> 於 2024年3月21日 週四 下午11:12寫道： >>> >>>> Hi Chia-Ping, >>>> >>>> Thanks for letting me know. >>>> >>>> Is this a regression from the 3.5.0 release? Can we update the "Affects >>>> Version/s" field on JIRA? >>>> >>>> Thanks, >>>> >>>> >>>> On Thu, Mar 21, 2024 at 5:06 PM Chia-Ping Tsai <chia7...@gmail.com> >>> wrote: >>>> >>>>> hi Manikumar, >>>>> >>>>> There is a bug fix which needs to be backport to 3.6 ( >>>>> https://issues.apache.org/jira/browse/KAFKA-16341) >>>>> >>>>> It fixes the incorrect offset of max timestamp in non-compress path. >>> The >>>>> other paths are already fixed by >>>>> https://issues.apache.org/jira/browse/KAFKA-16342. >>>>> >>>>> Personally, we should backport both fixes for all paths, and we can >>>>> complete the backport today. >>>>> >>>>> Sorry for bring this news to RC1. >>>>> >>>>> Best, >>>>> Chia-Ping >>>>> >>>>> >>>>> Manikumar <maniku...@apache.org> 於 2024年3月21日 週四 下午6:11寫道： >>>>> >>>>>> Hello Kafka users, developers and client-developers, >>>>>> >>>>>> This is the first candidate for release of Apache Kafka 3.6.2. >>>>>> >>>>>> This is a bugfix release with several fixes, including dependency >>>>>> version bumps for CVEs. >>>>>> >>>>>> Release notes for the 3.6.2 release: >>>>>> >>> https://home.apache.org/~manikumar/kafka-3.6.2-rc1/RELEASE_NOTES.html >>>>>> >>>>>> *** Please download, test and vote by Tuesday, March 26th >>>>>> >>>>>> Kafka's KEYS file containing PGP keys we use to sign the release: >>>>>> https://kafka.apache.org/KEYS >>>>>> >>>>>> * Release artifacts to be voted upon (source and binary): >>>>>> https://home.apache.org/~manikumar/kafka-3.6.2-rc1/ >>>>>> >>>>>> >>>>>> * Maven artifacts to be voted upon: >>>>>> >>> https://repository.apache.org/content/groups/staging/org/apache/kafka/ >>>>>> >>>>>> * Javadoc: >>>>>> https://home.apache.org/~manikumar/kafka-3.6.2-rc1/javadoc/ >>>>>> >>>>>> * Tag to be voted upon (off 3.6 branch) is the 3.6.2 tag: >>>>>> https://github.com/apache/kafka/releases/tag/3.6.2-rc1 >>>>>> >>>>>> * Documentation: >>>>>> https://kafka.apache.org/36/documentation.html >>>>>> >>>>>> * Protocol: >>>>>> https://kafka.apache.org/36/protocol.html >>>>>> >>>>>> * Successful Jenkins builds for the 3.6 branch: >>>>>> Unit/integration tests: >>>>>> >>>>>> >>>>> >>>> >>> https://ci-builds.apache.org/blue/organizations/jenkins/Kafka%2Fkafka/detail/3.6/159/tests >>>>>> (with few flaky failures) >>>>>> System tests: I will update system test results >>>>>> >>>>>> Thanks, >>>>>> Manikumar >>>>>> >>>>> >>>> >>>
