[jira] [Resolved] (KAFKA-15738) KRaft support in ConsumerWithLegacyMessageFormatIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-15738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-15738. --- Fix Version/s: 3.8.0 Resolution: Fixed > KRaft support in

Re: [DISCUSS] KIP-1014: Managing Unstable Metadata Versions in Apache Kafka

On Thu, Jan 11, 2024 at 10:43 PM Artem Livshits wrote: > > Hi Proven, > > I'd say that we should do 2 & 2. The idea is that for small features that > can be done and stabilized within a short period of time (with one or very > few commits) that's exactly what happens -- people interested in

Re: [VOTE] KIP-1005: Expose EarliestLocalOffset and TieredOffset

+1 non binding Thanks On Fri, Jan 12, 2024 at 1:31 AM Boudjelda Mohamed Said wrote: > > +1 (binding) > > > On Fri, Jan 12, 2024 at 1:21 AM Satish Duggana > wrote: > > > +1 (binding) > > > > Thanks, > > Satish. > > > > On Thu, 11 Jan 2024 at 17:52, Divij Vaidya > > wrote: > > > > > > +1

[jira] [Created] (KAFKA-16118) Coordinator unloading fails when replica is deleted

David Jacot created KAFKA-16118: --- Summary: Coordinator unloading fails when replica is deleted Key: KAFKA-16118 URL: https://issues.apache.org/jira/browse/KAFKA-16118 Project: Kafka Issue

Re: KIP-991: Allow DropHeaders SMT to drop headers by wildcard/regexp

Hi, Thanks, 100% agree, I fixed the description. Thanks, Roman Am Do., 11. Jan. 2024 um 18:27 Uhr schrieb Mickael Maison < mickael.mai...@gmail.com>: > Hi Roman, > > Thanks for the updates, this looks much better. > > Just a couple of small comments: > - The type of the field is listed as

Re: DISCUSS KIP-1011: Use incrementalAlterConfigs when updating broker configs by kafka-configs.sh

Hi Ziming, Thanks for the KIP! LGTM! Using incremental by defaul and fallback automatically if it's not supported is a good idea! One minor comment: 1. so I'm inclined to move it to incrementalAlterConfigs and "provide a flag" to still use alterConfigs for new client to interact with old

Re: [DISCUSS] KIP-1014: Managing Unstable Metadata Versions in Apache Kafka

I also agree with 2 & 2 with reasoning along the same lines as Artem. Thanks, Andrew > On 12 Jan 2024, at 09:15, Federico Valeri wrote: > > On Thu, Jan 11, 2024 at 10:43 PM Artem Livshits > wrote: >> >> Hi Proven, >> >> I'd say that we should do 2 & 2. The idea is that for small features

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #2565

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.6 #135

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.5 #104

See

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #2566

See Changes: -- [...truncated 346482 lines...] Gradle Test Run :core:test > Gradle Test Executor 94 > ZkMigrationClientTest > testCreateNewTopic() STARTED Gradle Test

[jira] [Resolved] (KAFKA-16119) kraft_upgrade_test system test is broken

[ https://issues.apache.org/jira/browse/KAFKA-16119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-16119. Resolution: Invalid After rebuilding my env from scratch I don't see this error anymore

Re: [DISCUSS] KIP-1014: Managing Unstable Metadata Versions in Apache Kafka

Hi, Thanks for the KIP. Reading the discussion, I think a lot of the confusion is due to the "unstable" naming. People are then trying to figure out when we think something is stable in the "this is battle-tested" sense. But this flag should not be about that. We can have an MV for a feature

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.7 #60

See

[jira] [Created] (KAFKA-16120) Partition reassignments in ZK migration dual write leaves stray partitions

David Mao created KAFKA-16120: - Summary: Partition reassignments in ZK migration dual write leaves stray partitions Key: KAFKA-16120 URL: https://issues.apache.org/jira/browse/KAFKA-16120 Project: Kafka

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.4 #173

See

[jira] [Created] (KAFKA-16119) kraft_upgrade_test system test is broken

Mickael Maison created KAFKA-16119: -- Summary: kraft_upgrade_test system test is broken Key: KAFKA-16119 URL: https://issues.apache.org/jira/browse/KAFKA-16119 Project: Kafka Issue Type: New

Re: [DISCUSS] KIP-890 Server Side Defense

Hi, Justine, Thanks for the reply. 101.4 "If the marker is written by the new client, we can as I mentioned in the last email guarantee that any EndTxn requests with the same epoch are from the same producer and the same transaction. Then we don't have to return a fenced error but can handle

[jira] [Resolved] (KAFKA-15816) Typos in tests leak network sockets

[ https://issues.apache.org/jira/browse/KAFKA-15816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-15816. - Fix Version/s: 3.8.0 Resolution: Fixed > Typos in tests leak network sockets >

[Kafka Streams], Processor API for KTable and KGroupedStream

Hello Is there any way in Kafka Streams API to have processors for KTable and KGroupedStream like KStream#transform? How to provide a complex processor for KTable or KGroupedStream which could provide way to not downstream events for some business logic? -- Igor Maznitsa email:

[jira] [Created] (KAFKA-16121) Partition reassignments in ZK migration dual write mode stalled until leader epoch incremented

David Mao created KAFKA-16121: - Summary: Partition reassignments in ZK migration dual write mode stalled until leader epoch incremented Key: KAFKA-16121 URL: https://issues.apache.org/jira/browse/KAFKA-16121

Re: [DISCUSS] KIP-1014: Managing Unstable Metadata Versions in Apache Kafka

Justine, For features that are not production-ready, they should have an additional configuration (not the metadata version) that enables/disables it. The MV specific features we ship are something we have to support and make sure we don't break going forward. Ismael On Fri, Jan 12, 2024 at

[jira] [Resolved] (KAFKA-16112) Review JMX metrics in Async Consumer and determine the missing ones

[ https://issues.apache.org/jira/browse/KAFKA-16112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Nee resolved KAFKA-16112. Resolution: Fixed These are the results of this ticket   |KAFKA-16113| |KAFKA-16116|

Re: [VOTE] 3.7.0 RC2

Hi Stanislav, Thanks for running this release! To verify, I: - Built from source using Java 11 with both: - - the 3.7.0-rc2 tag on GitHub - - the kafka-3.7.0-src.tgz artifact from https://home.apache.org/~stanislavkozlovski/kafka-3.7.0-rc2/ - Checked signatures and checksums - Ran the

Re: [DISCUSS] KIP-1014: Managing Unstable Metadata Versions in Apache Kafka

Hi Ismael, I debated including something about feature flags in my last comment, but maybe I should have. What you said makes sense. Justine On Fri, Jan 12, 2024 at 9:31 AM Ismael Juma wrote: > Justine, > > For features that are not production-ready, they should have an additional >

Re: [DISCUSS] KIP-890 Server Side Defense

Hi Jun, I can update the description. I believe your second point is mentioned in the KIP. I can add more text on this if it is helpful. > The delayed message case can also violate EOS if the delayed message comes in after the next addPartitionsToTxn request comes in. Effectively we may see a

Re: [DISCUSS] KIP-1014: Managing Unstable Metadata Versions in Apache Kafka

Hi Ismael, I think the concern I have about a MV for a feature that is not production ready is that it blocks any development/features with higher MV versions that could be production ready. I do see your point though. Previously MV/IBP was about pure broker compatibility and not about the

Re: [DISCUSS] KIP-1014: Managing Unstable Metadata Versions in Apache Kafka

I think using feature flags (whether we support a framework and tooling for feature flags or just an ad-hoc XyzEnabled flag) can be an alternative to this KIP. I think the value of this KIP is that it's trying to propose a systemic approach for gating functionality that may take multiple releases

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #2567

See

Re: [DISCUSS] KIP-890 Server Side Defense

Hi, Justine, Thanks for the reply. Sorry for the delay. I have a few more comments. 110. I think the motivation section could be improved. One of the motivations listed by the KIP is "This can happen when a message gets stuck or delayed due to networking issues or a network partition, the

Re: [DISCUSS] KIP-890 Server Side Defense

Hi Jun, In the case you describe, we would need to have a delayed request, send a successful EndTxn, and a successful AddPartitionsToTxn and then have the delayed EndTxn request go through for a given producer. I'm trying to figure out if it is possible for the client to transition if a previous

[jira] [Resolved] (KAFKA-16051) Deadlock on connector initialization

[ https://issues.apache.org/jira/browse/KAFKA-16051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-16051. - Fix Version/s: 3.8.0 Resolution: Fixed > Deadlock on connector initialization >

Re: [Kafka Streams], Processor API for KTable and KGroupedStream

`KGroupedStream` is just an "intermediate representation" to get a better flow in the DSL. It's not a "top level" abstraction like KStream/KTable. For `KTable` there is `transformValue()` -- there is no `transform()` because keying must be preserved -- if you want to change the keying you

Re: [PROPOSAL] Add commercial support page on website

François, thanks for starting this initiative. Personally, I don't think it's necessarily harmful for the project to add such a new page, however, I share the same concerns others raised already. I understand your motivation that people had issues finding commercial support, but I am not

[jira] [Created] (KAFKA-16122) TransactionsBounceTest -- server disconnected before response was received

Justine Olshan created KAFKA-16122: -- Summary: TransactionsBounceTest -- server disconnected before response was received Key: KAFKA-16122 URL: https://issues.apache.org/jira/browse/KAFKA-16122

Re: [DISCUSS] KIP-890 Server Side Defense

Hi, Justine, Thanks for the reply. I agree that we don't need to optimize for fencing during downgrades. Regarding consistency, there are two possible cases: (1) the prepare marker is written, but the endTxn response is not received by the client when the server downgrades; (2) the prepare

Re: [DISCUSS] KIP-890 Server Side Defense

(1) the prepare marker is written, but the endTxn response is not received by the client when the server downgrades (2) the prepare marker is written, the endTxn response is received by the client when the server downgrades. I think I am still a little confused. In both of these cases, the

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #2569

See

Re: [VOTE] 3.7.0 RC2

Hi Chris/Stanislav, I'm working on the 'Unable to find FetchSessionHandler' log problem (KAFKA-16029) and have put out a draft PR (https://github.com/apache/kafka/pull/15186). I will use the quickstart approach as a second means to reproduce/verify while I wait for the PR's Jenkins job to

Re: [VOTE] 3.7.0 RC2

Thanks, Kirk! @Stanislav--do you believe that this warrants a new RC? On Fri, Jan 12, 2024, 19:08 Kirk True wrote: > Hi Chris/Stanislav, > > I'm working on the 'Unable to find FetchSessionHandler' log problem > (KAFKA-16029) and have put out a draft PR ( >

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #2568

See Changes: -- [...truncated 461122 lines...] Gradle Test Run :core:test > Gradle Test Executor 92 > ZooKeeperClientTest > testConnection() STARTED Gradle Test Run

Re: [VOTE] 3.7.0 RC2

Hi Stanislav, I commented in the "Apache Kafka 3.7.0 Release" thread, but maybe you missed it. cross-posting here: There is a bug KAFKA-16101 reporting that "Kafka cluster will be unavailable during KRaft migration rollback". The impact for