Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.7 #50

See Changes: -- [...truncated 376297 lines...] > Task :core:test Gradle Test Run :core:test > Gradle Test Executor 92 > ZkMigrationIntegrationTest >

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2545

See

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

Hi Rowland, Thank you for the feedback. For the 2PC cases, the expectation is that the timeout on the client would be set to "effectively infinite", that would exceed all practical 2PC delays. Now I think that this flexibility is confusing and can be misused, I have updated the KIP to just say

Re: [DISCUSS] KIP-1012: The need for a Kafka 3.8.x release

Hi Colin, Thanks for the quick reply! > If we cannot get KIP-853 done in time for 3.8, then we'd move to have another > 3.x release. This is the crux of my concern, and this is satisfactory. This means that the "must-haves" are advisory only, and don't constitute a binding feature list or a

Re: Apache Kafka 3.7.0 Release

metadata is an internal gradle module. It is not used by clients. So I don't see why you would want to publish it (unless I'm misunderstanding something). best, Colin On Fri, Jan 5, 2024, at 10:05, Stanislav Kozlovski wrote: > Thanks for reporting the blockers, folks. Good job finding. > > I

Re: [DISCUSS] KIP-1012: The need for a Kafka 3.8.x release

Hi Justine, If there are more things you think are needed in 3.8 for migration, let's discuss in the VOTE thread. best, Colin On Fri, Jan 5, 2024, at 09:23, Justine Olshan wrote: > While I agree we should have this release and should vote on it soon, is it > worth determining the exact items

[jira] [Created] (KAFKA-16087) Sink connector dropping incorrect record when ErrantRecordReporter used asynchronously

Greg Harris created KAFKA-16087: --- Summary: Sink connector dropping incorrect record when ErrantRecordReporter used asynchronously Key: KAFKA-16087 URL: https://issues.apache.org/jira/browse/KAFKA-16087

Re: [VOTE] KIP-1012: The need for a Kafka 3.8.x release

I agree with Colin. Also, 4.0 would be started after 3.8 is branched (not after 3.8.0 is released). The rest looks good. Thanks! Ismael On Fri, Jan 5, 2024 at 11:27 PM Colin McCabe wrote: > Hi, > > Thanks for calling the vote, Josep. > > I re-checked this, and saw something that we missed

Re: [VOTE] KIP-1012: The need for a Kafka 3.8.x release

Gathering up some other feedback from the DISCUSS thread: - Please explicitly say that if we can't get the required features in in time, we'll have another 3.x release, following the usual time-based schedule - Please explicitly say that there may be other new features in 3.8 besides the

Re: [DISCUSS] KIP-1012: The need for a Kafka 3.8.x release

On Fri, Jan 5, 2024, at 11:28, Greg Harris wrote: > Hi Josep, > > Thanks for the KIP! I think that the motivations for having another > feature release before 4.0 are valid, as it seems that 3.7 is not > suitable as the last 3.x release. > I had a concern about the "Scope" section, in particular

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2544

See

Re: [VOTE] KIP-1012: The need for a Kafka 3.8.x release

Hi, Thanks for calling the vote, Josep. I re-checked this, and saw something that we missed updating. One thing we talked about earlier is that KIP-966 is actually not required for 3.8. What is required is some way of enabling unclean leader election by default in KRaft. (Which could be

Re: [VOTE] KIP-1004: Enforce tasks.max property in Kafka Connect

Hey Chris, Thanks for keeping KIP-987 in-mind. The current design of KIP-987 doesn't take tasks.max.enforce into account, but I think it may be possible to only allow the protocol upgrade when tasks.max.enforce is true if we were to try to enforce it. It may also be reasonable to just have a

Re: [DISCUSS] KIP-1012: The need for a Kafka 3.8.x release

Hi Josep, Thanks for the KIP! I think that the motivations for having another feature release before 4.0 are valid, as it seems that 3.7 is not suitable as the last 3.x release. I had a concern about the "Scope" section, in particular the language about "must haves", and the prevention of further

Re: Apache Kafka 3.7.0 Release

Thanks for reporting the blockers, folks. Good job finding. I have one ask - can anybody with Gradle expertise help review this small PR? https://github.com/apache/kafka/pull/15127 (+1, -1) In particular, we are wondering whether we need to publish module metadata as part of the gradle publishing

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2543

See

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

See

Re: [VOTE] KIP-1004: Enforce tasks.max property in Kafka Connect

Hi Yash, Thanks for raising the possibility of a more aggressive removal schedule for the tasks.max.enforce property now that it seems a 3.8.x branch is likely--I was wondering if someone would bring that up! I think I'd prefer to err on the side of caution and give users more time to adjust,

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

Hi all, Can we clarify any changes in the user-facing semantics for the CLI tool that would come about as a result of this KIP? I think the debate over the necessity of an opt-in flag, or waiting for 4.0.0, ultimately boils down to this. My understanding is that the only changes in semantics are

Re: [DISCUSS] KIP-1012: The need for a Kafka 3.8.x release

While I agree we should have this release and should vote on it soon, is it worth determining the exact items we need before we vote? Just so we are all in agreement? There is still some discussion on the road to 4.0 thread that may be worth having here. On Fri, Jan 5, 2024 at 1:25 AM Josep Prat

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

See

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

Hi Roman, Thanks for the KIP! This would be a useful improvement. Ideally you want to make a concerte proposal in the KIP instead of listing a series of options. Currently the KIP seems to list two alternatives. Also a KIP focuses on the API changes rather than on the pure implementation. It

[jira] [Resolved] (KAFKA-15922) Add MetadataVersion for JBOD

[ https://issues.apache.org/jira/browse/KAFKA-15922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Proven Provenzano resolved KAFKA-15922. --- Resolution: Fixed > Add MetadataVersion for JBOD > > >

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

Hey folks, I am starting a discussion thread for managing unstable metadata versions in Apache Kafka. https://cwiki.apache.org/confluence/display/KAFKA/KIP-1014%3A+Managing+Unstable+Metadata+Versions+in+Apache+Kafka This KIP is actually already implemented in 3.7 with PR

Re: Apache Kafka 3.7.0 Release

We have potentially one more blocker https://issues.apache.org/jira/browse/KAFKA-16082 which might cause a data loss scenario with JBOD in KRaft. Initial analysis thought this is a problem and further review looks like it isn't but we are continuing to dig into the issue to ensure that it isn't.

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2542

See

Re: Apache Kafka 3.7.0 Release

One more blocker (memory leak) for 3.7: https://issues.apache.org/jira/browse/KAFKA-16086 -Matthias On 1/4/24 9:53 PM, Stanislav Kozlovski wrote: Thanks Apoorv, I was going to update the mailing thread as well. Major kudos to Apoorv for the thorough work debugging and getting to the bottom

Re: [VOTE] KIP-1007: Introduce Remote Storage Not Ready Exception

Thanks Kamal for the KIP. +1 (binding) On Fri, 5 Jan 2024 at 17:04, Divij Vaidya wrote: > > +1 (binding) > > -- > Divij Vaidya > > > > On Thu, Dec 21, 2023 at 10:30 AM Luke Chen wrote: > > > Hi Kamal, > > > > Thanks for the KIP. > > +1 (binding) from me. > > > > Luke > > > > On Thu, Dec 21,

Re: [DISCUSS] KIP-1007: Introduce Remote Storage Not Ready Exception

Thank you for addressing my concerns Kamal. Though, instead of the KIP, I actually was suggesting to add it in JavaDoc so that someone looking at the exception is able to understand what it means. We can discuss that during the PR review though. The KIP looks good to me. -- Divij Vaidya On

Re: [VOTE] KIP-1007: Introduce Remote Storage Not Ready Exception

+1 (binding) -- Divij Vaidya On Thu, Dec 21, 2023 at 10:30 AM Luke Chen wrote: > Hi Kamal, > > Thanks for the KIP. > +1 (binding) from me. > > Luke > > On Thu, Dec 21, 2023 at 4:51 PM Christo Lolov > wrote: > > > Heya Kamal, > > > > The proposed change makes sense to me as it will be a more

Re: [VOTE] KIP-1012: The need for a Kafka 3.8.x release

+1 from me. Den fre 5 jan. 2024 kl 10:33 skrev Josep Prat : > Hi all, > > I'd like to start a vote on KIP-1012: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release > > Discussion thread is here: >

[jira] [Created] (KAFKA-16086) Kafka Streams has RocksDB native memory leak

Lucas Brutschy created KAFKA-16086: -- Summary: Kafka Streams has RocksDB native memory leak Key: KAFKA-16086 URL: https://issues.apache.org/jira/browse/KAFKA-16086 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-1007: Introduce Remote Storage Not Ready Exception

Thanks for the KIP Kamal, LGTM. On Tue, 26 Dec 2023 at 10:23, Kamal Chandraprakash wrote: > > Hi Divij, > > Thanks for reviewing the KIP! I've updated the KIP with the below > documentation. Let me know if it needs to be changed: > > The consumer can read the local data as long as it knows the

[VOTE] KIP-1012: The need for a Kafka 3.8.x release

Hi all, I'd like to start a vote on KIP-1012: https://cwiki.apache.org/confluence/display/KAFKA/KIP-1012%3A+The+need+for+a+Kafka+3.8.x+release Discussion thread is here: https://lists.apache.org/thread/kvdp2gmq5gd9txkvxh5vk3z2n55b04s5 Thanks! --- Josep Prat Open Source Engineering Director,

Re: [DISCUSS] KIP-1012: The need for a Kafka 3.8.x release

Hi Colin, Sorry for being quiet these last days (PTO). I will start the vote thread right away. Best, --- Josep Prat Open Source Engineering Director, aivenjosep.p...@aiven.io | +491715557497 | aiven.io Aiven Deutschland GmbH Alexanderufer 3-7, 10117 Berlin Geschäftsführer: Oskari Saarenmaa

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2541

See

[jira] [Created] (KAFKA-16085) remote copy lag bytes/segments metrics don't update all topic value

Luke Chen created KAFKA-16085: - Summary: remote copy lag bytes/segments metrics don't update all topic value Key: KAFKA-16085 URL: https://issues.apache.org/jira/browse/KAFKA-16085 Project: Kafka