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

See

Re: [DISCUSS] Apache Kafka 3.8.0 release

Sounds good, thanks Josep! Ismael On Wed, May 29, 2024 at 7:51 AM Josep Prat wrote: > Hi Ismael, > > I think your proposal makes more sense than mine. The end goal is to try to > get these 2 KIPs in 3.8.0 if possible. I think we can also achieve this by > not delaying the general feature freeze

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

See

Re: standalone race condition?

Hi John, Thanks for your question! I wasn't able to identify anything obviously wrong from your logfile and visible configurations. REST timeouts are something that we have ongoing problems with, and they're usually caused by blocking plugins. You can capture some additional diagnostics with `js

[jira] [Resolved] (KAFKA-16790) Calls to RemoteLogManager are made before it is configured

[ https://issues.apache.org/jira/browse/KAFKA-16790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-16790. --- Fix Version/s: 3.8.0 3.7.1 Resolution: Fixed > Calls to RemoteLogManager a

[jira] [Created] (KAFKA-16864) Copy on write in the Optimized Uniform Assignor

Ritika Reddy created KAFKA-16864: Summary: Copy on write in the Optimized Uniform Assignor Key: KAFKA-16864 URL: https://issues.apache.org/jira/browse/KAFKA-16864 Project: Kafka Issue Type: S

[jira] [Created] (KAFKA-16863) Consider removing `default.` prefix for exception handler config

Matthias J. Sax created KAFKA-16863: --- Summary: Consider removing `default.` prefix for exception handler config Key: KAFKA-16863 URL: https://issues.apache.org/jira/browse/KAFKA-16863 Project: Kafka

[jira] [Created] (KAFKA-16862) Refactor ConsumerTaskTest to be deterministic and avoid tight loops

Greg Harris created KAFKA-16862: --- Summary: Refactor ConsumerTaskTest to be deterministic and avoid tight loops Key: KAFKA-16862 URL: https://issues.apache.org/jira/browse/KAFKA-16862 Project: Kafka

[jira] [Resolved] (KAFKA-16771) First log directory printed twice when formatting storage

[ https://issues.apache.org/jira/browse/KAFKA-16771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16771. Fix Version/s: 3.8.0 Resolution: Fixed > First log directory printed twice when for

[jira] [Created] (KAFKA-16861) Don't convert to group to classic if the size is larger than group max size

Chia-Ping Tsai created KAFKA-16861: -- Summary: Don't convert to group to classic if the size is larger than group max size Key: KAFKA-16861 URL: https://issues.apache.org/jira/browse/KAFKA-16861 Proje

Re: [VOTE] KIP-939: Support Participation in 2PC

+1 Thanks for the KIP! On Wed, Mar 13, 2024 at 5:13 AM Omnia Ibrahim wrote: > I had a look at the discussion thread and the KIP looks exciting. > +1 non-binding > > Best > Omnia > > On 1 Dec 2023, at 19:06, Artem Livshits > wrote: > > Hello, > > This is a voting thread for > > https://cwiki.apa

Re: [DISCUSS] KIP-891: Running multiple versions of Connector plugins

Hi Greg, First, an apology! I mistakenly assumed that each plugin appeared only once in the responses from GET /connector-plugins?connectorsOnly=false. Thank you for correcting me and pointing out that all versions of each plugin appear in that response, which does indeed satisfy my desire for use

Re: [DISCUSS] Apache Kafka 3.8.0 release

Hi Calvin, Thanks for the update. Then it makes sense to not delay the 3.8.0 release and check case by case which commits if the mentioned KIPs should be cherry picked to the branch. This means the dates stay. Today EoD is the deadline for feature freeze. I'll cut the new branch before Friday EoD

Re: [DISCUSS] Apache Kafka 3.8.0 release

Hi Regarding the KIP-966, the implementation is split into 2 parts. Part 1 where we introduce the Eligible Leader Replicas to help increase the data durability is pretty close to finish. We have 1 feature PR pending. Currently, Colin McCabe is helping the review and hopefully we can get it merged w

Re: [DISCUSS] KIP-891: Running multiple versions of Connector plugins

Hey Chris, Thanks for your thoughts. > Won't it still only expose the > latest version for each plugin, instead of the range of versions available? Here is a snippet of the current output of the GET /connector-plugins?connectorsOnly=false endpoint, after I installed two versions of the debezium

Re: [DISCUSS] Apache Kafka 3.8.0 release

Hi, Regarding KIP-1033, we are not opposed to a slight delay. One of the related PRs was merged today. If possible, we would like to proceed in the same manner as with KIP-853 and KIP-966. regards, De : Josep Prat Envoyé : mercredi 29 mai 2024 16:51 À : dev@kafka.apache.org Objet : [EXT] Re:

[jira] [Resolved] (KAFKA-16722) Add ConsumerGroupPartitionAssignor interface

[ https://issues.apache.org/jira/browse/KAFKA-16722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-16722. - Reviewer: David Jacot Resolution: Fixed > Add ConsumerGroupPartitionAssignor interface > -

Re: [VOTE] KIP-1040: Improve handling of nullable values in InsertField, ExtractField, and other transformations

Hi Mario, +1 (binding) Thanks for the KIP! Mickael On Mon, May 27, 2024 at 12:06 PM Mario Fiore Vitale wrote: > > After 7 days I received only one vote. Should I suppose this will not be > approved? > > On Mon, May 20, 2024 at 4:14 PM Chris Egerton > wrote: > > > Thanks for the KIP! +1 (bindin

Re: [DISCUSS] KIP-891: Running multiple versions of Connector plugins

Hi Greg, I'm confused about the behavior for GET /connector-plugins?connectorsOnly=false. Won't it still only expose the latest version for each plugin, instead of the range of versions available? I'm hoping we can provide a flow where people need at most two REST calls to discover 1) the complet

Re: [DISCUSS] Apache Kafka 3.8.0 release

Hi Ismael, I think your proposal makes more sense than mine. The end goal is to try to get these 2 KIPs in 3.8.0 if possible. I think we can also achieve this by not delaying the general feature freeze, but rather by cherry picking the future commits on these features to the 3.8 branch. So I woul

standalone race condition?

Hi Folks, I quite often get this issue with the kafka standalone and I really need it fixing as I can't continue working like this so any help would be gratefully received. Scenario: Server starts OK. Deploy a connector or two using the REST API. Then I deploy the JDBC connector and sometim

[jira] [Resolved] (KAFKA-16705) the flag "started" of RaftClusterInstance is false even though the cluster is started

[ https://issues.apache.org/jira/browse/KAFKA-16705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16705. Fix Version/s: 3.8.0 Resolution: Fixed > the flag "started" of RaftClusterInstance

Re: [DISCUSS] Apache Kafka 3.8.0 release

Hi Josep, It's generally a bad idea to push these dates because the scope keeps increasing then. If there are features that need more time and we believe they are essential for 3.8 due to its special nature as the last release before 4.0, we should allow them to be cherry-picked to the release bra

Re: [DISCUSS] Apache Kafka 3.8.0 release

Hi Mickael, I'd need some help from @José Armando García Sancio and Calvin Liu (explicitly added to the email) to have a better estimation on how much effort is left. Regarding KIP-853, it seems a good deal of tasks are assigned and some seem to be in progress (regardless of what the status says)

Re: [DISCUSS] Apache Kafka 3.8.0 release

Hi Josep, The point of the 3.8.0 release was to bridge feature gaps we identified between ZooKeeper and KRaft based Kafka clusters. In KIP-1012, we had identified 2 features we needed before 4.0: KIP-853 and unclean leader elections (KIP-966?). Can we have a status update on both of these feature

[jira] [Resolved] (KAFKA-16569) Target Assignment Format Change

[ https://issues.apache.org/jira/browse/KAFKA-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-16569. - Resolution: Won't Do > Target Assignment Format Change > --- > >

[jira] [Resolved] (KAFKA-16832) LeaveGroup API for upgrading ConsumerGroup

[ https://issues.apache.org/jira/browse/KAFKA-16832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-16832. - Fix Version/s: 3.8.0 Resolution: Fixed > LeaveGroup API for upgrading ConsumerGroup > ---

Re: [DISCUSS] KIP-655: Add deduplication processor in kafka-streams

Hi everyone, I've just made a (small) change to this KIP about an implementation detail. Please let me know your thoughts. Thank you, Ayoub Le lun. 20 mai 2024 à 21:13, Ayoub a écrit : > Hello, > > Following a discussion on community slack channel, I would like to revive > the discussion on th

Re: [DISCUSS] Apache Kafka 3.8.0 release

A correction on the dates as they should be: - Feature freeze is on June 12th (you wrote May before) - code freeze is on June 26th So these are the new proposed deadlines. Best, On Wed, May 29, 2024 at 12:48 PM Luke Chen wrote: > Hi Josep, > > Thanks for raising this. > I'm +1 for delaying som

Re: [DISCUSS] Apache Kafka 3.8.0 release

Hi Josep, Thanks for raising this. I'm +1 for delaying some time to have features completed. But I think we might need to make it clear, what's the updated feature freeze date/code freeze date? Is this correct? - Feature freeze is on May 12th - Code freeze is June 26th Thanks. Luke On Wed, May

Re: [DISCUSS] KIP-1035: StateStore managed changelog offsets

I've updated the KIP with the following: - Deprecation of StateStore#managesOffsets - Change StateStore#commit to throw UnsupportedOperationException when called from a Processor (via AbstractReadWriteDecorator) - Updated consumer rebalance lag computation strategy

Re: [DISCUSS] Apache Kafka 3.8.0 release

Hi Kafka developers, Given the fact we have a couple of KIPs that are halfway through their implementation and it seems it's a matter of days (1 or 2 weeks) to have them completed. What would you think if we delay feature freeze and code freeze by 2 weeks? Let me know your thoughts. Best, On Tue

Re: [DISCUSS] KIP-1035: StateStore managed changelog offsets

Hi everyone, Sorry I haven't got around to updating the KIP yet. Now that I've wrapped up KIP-989, I'm going to be working on 1035 starting today. I'll update the KIP first, and then call a vote. Regards, Nick On Wed, 29 May 2024 at 07:25, Bruno Cadonna wrote: > Totally agree on moving forwar

Re: [DISCUSS] KIP-1049: Add config log.summary.interval.ms to Kafka Streams

Sure, as I said I'm supportive of this KIP. Just wanted to mention how the issue could be mitigated in the meantime since the description made it sound like you were suffering from excessive logs right now. Apologies if I misinterpreted that. I do think it would be nice to have a general setting f

[jira] [Resolved] (KAFKA-16399) Add JBOD support in tiered storage

[ https://issues.apache.org/jira/browse/KAFKA-16399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-16399. --- Fix Version/s: 3.8.0 Resolution: Fixed > Add JBOD support in tiered storage > ---