Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.9 #167

See

[jira] [Resolved] (KAFKA-18712) Move Endpoint to server module

[ https://issues.apache.org/jira/browse/KAFKA-18712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18712. Fix Version/s: 4.1.0 Resolution: Fixed > Move Endpoint to server module > -

Re: [DISCUSS] KIP-1124: Providing a clear Kafka Client upgrade path

Thanks all. Seems we are converging. :) Again, sorry to the previous very long email, but I thought it's important to paint a full end-to-end picture. I agree that we should try to keep it simple to the extend reasonable possible! If we really want to suggest just 2.8 / 3.9 as bridge version

Re: [DISCUSS] KIP-1134: Virtual Clusters in Kafka

Hi Victor, > Yes, we didn't plan for this originally, so it would be the administrator's responsibility to migrate existing ACLs, however thinking about it, the migration could be quite simple (essentially we would just need to use the same ACLs but move them to under VC1 so they're not global). T

[jira] [Resolved] (KAFKA-18281) Kafka (3.9.0) is improperly validating non-advertised listeners for routable controller addresses

[ https://issues.apache.org/jira/browse/KAFKA-18281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio resolved KAFKA-18281. Resolution: Fixed > Kafka (3.9.0) is improperly validating non-adv

[jira] [Resolved] (KAFKA-18856) 3.9 broker unable to join dynamic quorum with 4.0 controller

[ https://issues.apache.org/jira/browse/KAFKA-18856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] TengYao Chi resolved KAFKA-18856. - Resolution: Invalid > 3.9 broker unable to join dynamic quorum with 4.0 controller > ---

Re: [VOTE] KIP-1127: Flexible Windows for Late Arriving Data

+1 (binding) On 2/18/25 8:58 AM, Lucas Brutschy wrote: +1 (binding) Thanks for the KIP! On Wed, Feb 5, 2025 at 8:06 AM Sophie Blee-Goldman wrote: +1 (binding) Thanks for the KIP! Neat and practical idea On Tue, Feb 4, 2025 at 10:52 AM Almog Gavra wrote: Hello All, I'd like to start a

Jenkins build is still unstable: Kafka » Kafka PowerPC Daily » test-powerpc #220

See

[jira] [Created] (KAFKA-18859) honor the error message of UnregisterBrokerResponse

Chia-Ping Tsai created KAFKA-18859: -- Summary: honor the error message of UnregisterBrokerResponse Key: KAFKA-18859 URL: https://issues.apache.org/jira/browse/KAFKA-18859 Project: Kafka Issue

Re: New PR workflow in KAFKA-18748

> > Can we merge the PR if only flaky or new tests fail? We certainly cannot merge if new tests fail - the goal is to ensure new tests are solid. For the flaky ones, I'm not sure how we intend to use these. I would prefer if we only merge when the PR status is green. Otherwise, we often end up m

[jira] [Created] (KAFKA-18858) Refactor FeatureControlManager to avoid using uninitialized MV

Chia-Ping Tsai created KAFKA-18858: -- Summary: Refactor FeatureControlManager to avoid using uninitialized MV Key: KAFKA-18858 URL: https://issues.apache.org/jira/browse/KAFKA-18858 Project: Kafka

[jira] [Resolved] (KAFKA-17937) Use ValueSource to refactor AbstractFetcherThreadTest to eliminate unnecessary skip tests

[ https://issues.apache.org/jira/browse/KAFKA-17937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17937. Fix Version/s: 4.1.0 Resolution: Fixed > Use ValueSource to refactor AbstractFetche

Re: New PR workflow in KAFKA-18748

Thanks David - this is another important improvement to our CI pipeline and is super helpful for the project and community. Ismael On Mon, Feb 24, 2025 at 2:15 PM David Arthur wrote: > Hey everyone, just wanted to inform you all that we just merged KAFKA-18748 > > https://github.com/apache/kafk

Re: [VOTE] 4.0.0 RC0

If the purpose of this is not to vote but just to evaluate the RC then I think it would be better to not use the [VOTE] tag for the subject as that is super confusing. On Mon, Feb 24, 2025 at 10:45 AM Ismael Juma wrote: > Hi Mickael, > > This was addressed in the original message: > > "This is t

Re: New PR workflow in KAFKA-18748

hi David Thanks for all your improvement. I do love the new test suites! one small question: Can we merge the PR if only flaky or new tests fail? Sometimes, I list tickets for flaky (or unrelated) tests before merging. However, since we now have a separate test suite for stable tests (non-flaky,

New PR workflow in KAFKA-18748

Hey everyone, just wanted to inform you all that we just merged KAFKA-18748 https://github.com/apache/kafka/pull/18770 This splits our CI workflow into more parallel jobs which run subsets of the tests with different settings. The JUnit tests are now split into "new", "flaky", and the remainder.

Re: [DISCUSS] KIP-1121: Compression acceleration in Kafka

Hi Olasoji, Thanks for the update. 1. Could you add these as code examples to the KIP, and not as prose? See [1-3] for some examples of well-written public interfaces. 2. I find the proposed API surface area excessive, and think we need to narrow it down. Looking at what's merged on trunk right

[jira] [Resolved] (KAFKA-15928) Flaky test - testBalancePartitionLeaders - QuorumControllerTest

[ https://issues.apache.org/jira/browse/KAFKA-15928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lianet Magrans resolved KAFKA-15928. Resolution: Duplicate Marking this as dup of KAFKA-18844 (PR out)  > Flaky test - testBal

[jira] [Created] (KAFKA-18857) Avoid authorization check in the group coordinator

Dongnuo Lyu created KAFKA-18857: --- Summary: Avoid authorization check in the group coordinator Key: KAFKA-18857 URL: https://issues.apache.org/jira/browse/KAFKA-18857 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-983: Full speed async processing during rebalance

Hi David, Philip, We're a bit more then a year further. Is KIP-983 still something you'd like to work on? Kind regards,     Erik. Op 15-10-2023 om 16:43 schreef David Jacot: Hi Erik, Our current target is to have a preview in 3.7. This is subject to change though. Best, David Le dim. 15

Re: [DISCUSS] KIP-1124: Flexible Windows for Late Arriving Data

Good call out, thanks Matthias! I've updated the example image in the KIP and called out specifically that window ends are exclusive in the corresponding javadocs. - Almog On Thu, Feb 20, 2025 at 5:45 PM Matthias J. Sax wrote: > Hi, > > I was just re-reading to KIP in order to vote and notices

Re: [DISCUSS] KIP-1124: Providing a clear Kafka Client upgrade path

Hello everyone, Thanks Chia-Ping for the advice. I’ve created a table to cover all upgrade path scenarios, hoping it provides more clarity. Please let me know if I’ve misunderstood anything. I appreciate any corrections! Additionally, as I recently updated the KIP title, here’s the new link: ht

Re: [DISCUSS] KIP-1134: Virtual Clusters in Kafka

Hi Greg, 3. It sounds like some of the complication you're mentioning comes from the physical topic names and physical location on disk; that's sorta why I brought up (2). If we transform the log layer to store things by UUID rather than by topic name, we are then free to develop whatever mapping

Re: [VOTE] 4.0.0 RC0

Hi Mickael, This was addressed in the original message: "This is the first candidate for release of Apache Kafka 4.0.0. We still have some remaining blockers but we figured that getting a first release candidate will help the community to test this major release." There are a large number of cha

[jira] [Created] (KAFKA-18856) 3.9 broker unable to join dynamic quorum with 4.0 controller

TengYao Chi created KAFKA-18856: --- Summary: 3.9 broker unable to join dynamic quorum with 4.0 controller Key: KAFKA-18856 URL: https://issues.apache.org/jira/browse/KAFKA-18856 Project: Kafka I

Re: [VOTE] 4.0.0 RC0

Hi David, I see we still have a few open Jiras marked as blockers for 4.0.0: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=325421614#ReleasePlan4.0.0-OpenIssues Are we expecting another RC soon? Or can this vote pass and these Jiras are moved to 4.1.0? Thanks, Mickael On Sun,

[jira] [Created] (KAFKA-18855) MemoryRecords should have slice API

Apoorv Mittal created KAFKA-18855: - Summary: MemoryRecords should have slice API Key: KAFKA-18855 URL: https://issues.apache.org/jira/browse/KAFKA-18855 Project: Kafka Issue Type: Sub-task

Re: [DISCUSS] KIP-1133: AK Documentation and Website in Markdown

Hi Harish, This is definitively something we want to do! MM1. One aspect to keep in mind in terms of compatibility is whether existing links will still work. Thousands of online resources link to the Apache Kafka website. Is it possible to keep all links working? MM2. A bunch of sections are gen

Re: [DISCUSS] KIP-1133: AK Documentation and Website in Markdown

Hi Harish, Thanks for the KIP! Great initiative! Do you plan to have a development version of the website online in parallel to the old HTML version? I understand that locally with the markdown files and an markdown editor, we see the rough structure of the docs (which is already an improve

[jira] [Resolved] (KAFKA-18848) Flaky test CooperativeConsumerCoordinatorTest#testOutdatedCoordinatorAssignment

[ https://issues.apache.org/jira/browse/KAFKA-18848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lianet Magrans resolved KAFKA-18848. Resolution: Duplicate > Flaky test > CooperativeConsumerCoordinatorTest#testOutdatedCoord

[jira] [Resolved] (KAFKA-18828) Update share group metrics code in group coordinator

[ https://issues.apache.org/jira/browse/KAFKA-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18828. -- Fix Version/s: 4.1.0 Resolution: Fixed > Update share group metrics code in gro

[jira] [Resolved] (KAFKA-18779) Validate responses from broker in client for ShareFetch and ShareAcknowledge APIs.

[ https://issues.apache.org/jira/browse/KAFKA-18779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18779. -- Fix Version/s: 4.1.0 Resolution: Fixed > Validate responses from broker in clie

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.8 #149

See