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

See

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

See

[jira] [Resolved] (KAFKA-15250) DefaultBackgroundThread is running tight loop

[ https://issues.apache.org/jira/browse/KAFKA-15250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Nee resolved KAFKA-15250. Fix Version/s: (was: 3.8.0) Resolution: Fixed > DefaultBackgroundThread is running

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

See Changes: -- [...truncated 457704 lines...] Gradle Test Run :streams:test > Gradle Test Executor 91 > TasksTest >

Re: [VOTE] KIP-1013: Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7)

+1 binding Thanks! David On Wed, Jan 3, 2024 at 8:19 PM Ismael Juma wrote: > Hi Mickael, > > Good catch. I fixed that and one other (similar) case (they were remnants > of an earlier version of the proposal). > > Ismael > > On Wed, Jan 3, 2024 at 8:59 AM Mickael Maison > wrote: > > > Hi

Re: [PR] 3.7: Add documentation for Kafka 3.7 [kafka-site]

stanislavkozlovski merged PR #576: URL: https://github.com/apache/kafka-site/pull/576 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

Re: [PR] 3.7: Add documentation for Kafka 3.7 [kafka-site]

jolshan commented on PR #576: URL: https://github.com/apache/kafka-site/pull/576#issuecomment-1881984697 Sorry I was unclear. I meant to ask how to get a diff between versions. Looks like Colin did it though.  -- This is an automated message from the Apache Git Service. To respond to

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

See

Re: [PR] 3.7: Add documentation for Kafka 3.7 [kafka-site]

stanislavkozlovski commented on PR #576: URL: https://github.com/apache/kafka-site/pull/576#issuecomment-1881968438 @jolshan this is the way afaict, we re-generate everything and keep a copy of it under the appropriate `{release}/` folder -- This is an automated message from the Apache

[jira] [Created] (KAFKA-16095) Update list group state type filter to include the states for the new consumer group type

Ritika Reddy created KAFKA-16095: Summary: Update list group state type filter to include the states for the new consumer group type Key: KAFKA-16095 URL: https://issues.apache.org/jira/browse/KAFKA-16095

Re: Apache Kafka 3.7.0 Release

On an unrelated note, I found a blocker bug related to upgrades from 3.6 (and earlier) to 3.7. The JIRA is here: https://issues.apache.org/jira/browse/KAFKA-16094 Fix here: https://github.com/apache/kafka/pull/15153 best, Colin On Mon, Jan 8, 2024, at 14:47, Colin McCabe wrote: > Hi

Re: Apache Kafka 3.7.0 Release

Hi Ismael, I wasn't aware of that. If we are required to publish all modules, then this is working as intended. I am a bit curious if we've discussed why we need to publish the server modules to Sonatype. Is there a discussion about the pros and cons of this somewhere? regards, Colin On Mon,

[jira] [Created] (KAFKA-16094) 3.7 brokers must be able to register with 3.6 and earlier controllers

Colin McCabe created KAFKA-16094: Summary: 3.7 brokers must be able to register with 3.6 and earlier controllers Key: KAFKA-16094 URL: https://issues.apache.org/jira/browse/KAFKA-16094 Project: Kafka

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

Hey Colin, I had some offline discussions with Proven previously and it seems like he said something different so I'm glad I brought it up here. Let's clarify if we are ok with reordering unstable metadata versions :) Justine On Mon, Jan 8, 2024 at 1:56 PM Colin McCabe wrote: > On Mon, Jan

Re: Apache Kafka 3.7.0 Release

All modules are published to Sonatype - that's a requirement. You may be missing the fact that `core` is published as `kafka_2.13` and `kafka_2.12`. Ismael On Tue, Jan 9, 2024 at 12:00 AM Colin McCabe wrote: > Hi Ismael, > > It seems like both the metadata gradle module and the server-common

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

Hi Chris, Based on some of the offline discussions we had, people generally feel that major/minor releases have a large enough overhead that they don't want them more frequently than every 4 months. (Obviously dot releases are a different story) So Josep and I didn't want to raise the issue

Re: Apache Kafka 3.7.0 Release

Hi Ismael, It seems like both the metadata gradle module and the server-common module are getting published to Sonatype as separate artifacts, unless I'm misunderstanding something. Example: https://central.sonatype.com/search?q=kafka-server-common I don't see kafka-core getting published,

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

On Mon, Jan 8, 2024, at 13:19, Justine Olshan wrote: > Hey all, > > I was wondering how often we plan to update LATEST_PRODUCTION metadata > version. Is this something we should do as soon as the feature is complete > or something we do when we are releasing kafka. When is the time we abandon > a

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

Hey all, I was wondering how often we plan to update LATEST_PRODUCTION metadata version. Is this something we should do as soon as the feature is complete or something we do when we are releasing kafka. When is the time we abandon a MV so that other features can be unblocked? I am just

Re: Apache Kafka 3.7.0 Release

Hi all, Are you talking about publishing the artefacts to maven central? Looking at the history [1], it seems that the metadata module has been published since we have it. I also see other internal modules there too. [1]

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

Hi Colin, The idea isn't to hold up 4.0.0 any longer; in fact, it's the opposite. If things slip a bit with 3.8.0 and we take, for example, an extra month to deliver it (or even to cut the branch), I don't think this should necessarily translate to an extra month of latency between now and 4.0.0,

Re: Apache Kafka 3.7.0 Release

Hi Colin, I think you may have misunderstood what they mean by gradle metadata - it's not the Kafka metadata module. Ismael On Mon, Jan 8, 2024 at 9:45 PM Colin McCabe wrote: > Oops, hit send too soon. I see that #15127 was already merged. So we > should no longer be publishing :metadata as

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

Hi Proven, Thanks for the KIP. I think there is a need for this capability, for those of us who deploy from trunk (or branches dervied from trunk). With regard to "unstable.metadata.versions.enable": is this going to be a documented configuration, or an internal one? I am guessing we want it

Re: [DISCUSS] KIP-1015: Limit number of ssl connections in brokers

Hi zw, As you yourself wrote in the rejected alternatives section, the existing listener-specific connection limit already lets administrators limit the number of SSL connections (assuming that one listener is SSL and another is not). I don't understand the objection to just using that

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

On Fri, Jan 5, 2024, at 14:50, Greg Harris wrote: > 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

Re: Apache Kafka 3.7.0 Release

Oops, hit send too soon. I see that #15127 was already merged. So we should no longer be publishing :metadata as part of the clients artifacts, right? thanks, Colin On Mon, Jan 8, 2024, at 11:42, Colin McCabe wrote: > Hi Apporv, > > Please remove the metadata module from any artifacts

Re: Apache Kafka 3.7.0 Release

Hi Apporv, Please remove the metadata module from any artifacts published for clients. It is only used by the server. best, Colin On Sun, Jan 7, 2024, at 03:04, Apoorv Mittal wrote: > Hi Colin, > Thanks for the response. The only reason for asking the question of > publishing the metadata is

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

On Mon, Jan 8, 2024, at 09:05, Chris Egerton wrote: > Hi Josep, > > Thanks for the KIP! +1 (binding). > > One small nit: I don't think we necessarily have to hold ourselves to > releasing 4.0.0 "3 to 4 months after 3.8 branch is created" (quoting the > timeline section of the KIP). IMO it's fine

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

Thanks for the changes. +1 (binding) best, Colin On Sun, Jan 7, 2024, at 23:43, Josep Prat wrote: > Hi all, > > Thanks for your comments, > I reworded some parts of the KIP to express that: > - The KIP is to agree that we need at least one more minor version in the > 3.x series > - Explicitly

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

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

[jira] [Created] (KAFKA-16093) Spurious warnings logged to stderr about empty path annotations and providers not implementing provider interfaces

Chris Egerton created KAFKA-16093: - Summary: Spurious warnings logged to stderr about empty path annotations and providers not implementing provider interfaces Key: KAFKA-16093 URL:

Re: [PR] 3.7: Add documentation for Kafka 3.7 [kafka-site]

jolshan commented on PR #576: URL: https://github.com/apache/kafka-site/pull/576#issuecomment-1881640198 `+355,890`  Is there a way to update just what is new -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

Re: Apache Kafka 3.7.0 Release

I've almost got an RC candidate out to test. I just need a. review on the kafka-site repo to update the website with the appropriate 3.7 subpages - https://github.com/apache/kafka-site/pull/576/ On Mon, Jan 8, 2024 at 10:05 AM Lucas Brutschy wrote: > Hi, > > we have fixed one memory leak in

Re: [PR] 3.7: Add documentation for Kafka 3.7 [kafka-site]

stanislavkozlovski commented on PR #576: URL: https://github.com/apache/kafka-site/pull/576#issuecomment-1881629932 cc @showuon @C0urante @satishd could you perhaps help review? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

Re: [PR] 3.7: Add documentation for Kafka 3.7 [kafka-site]

stanislavkozlovski commented on code in PR #576: URL: https://github.com/apache/kafka-site/pull/576#discussion_r1445131803 ## 37/javadoc/index.html: ## @@ -0,0 +1,265 @@ + + + + +Overview (kafka 3.7.0-SNAPSHOT API) Review Comment: ok figured out why. re-generated with the

Re: [PR] 3.7: Add documentation for Kafka 3.7 [kafka-site]

stanislavkozlovski commented on code in PR #576: URL: https://github.com/apache/kafka-site/pull/576#discussion_r1445116548 ## 37/javadoc/index.html: ## @@ -0,0 +1,265 @@ + + + + +Overview (kafka 3.7.0-SNAPSHOT API) Review Comment: note that this is 3.7.0-SNAPSHOT similar

[PR] 3.7: Add documentation for Kafka 3.7 [kafka-site]

stanislavkozlovski opened a new pull request, #576: URL: https://github.com/apache/kafka-site/pull/576 This patch adds the generated 3.7.0 release docs as mentioned in the [wiki](https://cwiki.apache.org/confluence/display/KAFKA/Release+Process#ReleaseProcess-Websiteupdateprocess) --

[DISCUSS] KIP-853: KRaft Controller Membership Changes

Hi all, KIP-853: KRaft Controller Membership Changes is ready for another round of discussion. There was a previous discussion thread at https://lists.apache.org/thread/zb5l1fsqw9vj25zkmtnrk6xm7q3dkm1v I have changed the KIP quite a bit since that discussion. The core idea is still the same. I

[jira] [Created] (KAFKA-16092) Queues for Kafka

Andrew Schofield created KAFKA-16092: Summary: Queues for Kafka Key: KAFKA-16092 URL: https://issues.apache.org/jira/browse/KAFKA-16092 Project: Kafka Issue Type: Improvement

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

See

[jira] [Resolved] (KAFKA-15846) Review consumer leave group request best effort and response handling

[ https://issues.apache.org/jira/browse/KAFKA-15846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lianet Magrans resolved KAFKA-15846. Fix Version/s: (was: 3.8.0) Resolution: Duplicate > Review consumer leave

[jira] [Resolved] (KAFKA-15542) Release member assignments on errors

[ https://issues.apache.org/jira/browse/KAFKA-15542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lianet Magrans resolved KAFKA-15542. Fix Version/s: 3.7.0 (was: 3.8.0) Resolution: Fixed Fixed

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

Hi Josep, Thanks for the KIP! +1 (binding). One small nit: I don't think we necessarily have to hold ourselves to releasing 4.0.0 "3 to 4 months after 3.8 branch is created" (quoting the timeline section of the KIP). IMO it's fine to leave some wiggle room for the 4.0.0 release without codifying

Re: [VOTE] KIP-971: Expose replication-offset-lag MirrorMaker2 metric

Hi Elxan, +1 (non-binding) Thanks for the KIP, this will be a very useful metric for MM! Daniel Elxan Eminov ezt írta (időpont: 2024. jan. 7., V, 2:17): > Hi all, > Bumping this for visibility > > On Wed, 3 Jan 2024 at 18:13, Elxan Eminov wrote: > > > Hi All, > > I'd like to initiate a vote

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

Thanks Josep for leading the KIP and building consensus on 3.8! +1 (binding) Greg On Sun, Jan 7, 2024 at 11:45 PM Josep Prat wrote: > > Hi all, > > Thanks for your comments, > I reworded some parts of the KIP to express that: > - The KIP is to agree that we need at least one more minor version

[jira] [Resolved] (KAFKA-15719) KRaft support in OffsetsForLeaderEpochRequestTest

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

[jira] [Resolved] (KAFKA-15515) Remove duplicated integration tests for new consumer

[ https://issues.apache.org/jira/browse/KAFKA-15515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lianet Magrans resolved KAFKA-15515. Fix Version/s: (was: 4.0.0) Resolution: Not A Problem

[jira] [Resolved] (KAFKA-15725) KRaft support in FetchRequestTest

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

[jira] [Resolved] (KAFKA-16016) Migrate utility scripts to kafka codebase

[ https://issues.apache.org/jira/browse/KAFKA-16016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vedarth Sharma resolved KAFKA-16016. Reviewer: Manikumar Resolution: Fixed > Migrate utility scripts to kafka codebase >

[VOTE] KIP-995: Allow users to specify initial offsets while creating connectors

Hi All, I would like to start a vote on KIP-995. https://cwiki.apache.org/confluence/display/KAFKA/KIP-995%3A+Allow+users+to+specify+initial+offsets+while+creating+connectors Discussion thread - https://lists.apache.org/thread/msorbr63scglf4484yq764v7klsj7c4j Thanks! Ashwin

[jira] [Resolved] (KAFKA-15325) Integrate topicId in OffsetFetch and OffsetCommit async consumer calls

[ https://issues.apache.org/jira/browse/KAFKA-15325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lianet Magrans resolved KAFKA-15325. Resolution: Duplicate > Integrate topicId in OffsetFetch and OffsetCommit async consumer

Re: Requesting permissions to contribute to Apache Kafka

Thanks Josep. On Mon, Jan 8, 2024 at 7:38 PM Josep Prat wrote: > Hi Abhinav, > > This one I could find :) > > You are now all set! Happy contributing! > > Best, > > On Mon, Jan 8, 2024 at 2:39 PM Abhinav Dixit > wrote: > > > Hi Josep, > > Thanks for the quick response. My WIKI ID is adixit,

Re: Requesting permissions to contribute to Apache Kafka

Hi Abhinav, This one I could find :) You are now all set! Happy contributing! Best, On Mon, Jan 8, 2024 at 2:39 PM Abhinav Dixit wrote: > Hi Josep, > Thanks for the quick response. My WIKI ID is adixit, sorry for the > confusion. > Thanks, > Abhinav > > On Mon, Jan 8, 2024 at 6:59 PM Josep

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

See

Re: Requesting permissions to contribute to Apache Kafka

Hi Josep, Thanks for the quick response. My WIKI ID is adixit, sorry for the confusion. Thanks, Abhinav On Mon, Jan 8, 2024 at 6:59 PM Josep Prat wrote: > Hi Abhinav, > Thanks for your interest in Apache Kafka. > I could set up your Jira account accordingly, but I can't find your Wiki ID > in

Re: Requesting permissions to contribute to Apache Kafka

Hi Abhinav, Thanks for your interest in Apache Kafka. I could set up your Jira account accordingly, but I can't find your Wiki ID in the system. Can you confirm you created it and named it "adixitconfluent"? Best, On Mon, Jan 8, 2024 at 2:10 PM Abhinav Dixit wrote: > Hi Team, > I am writing

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.7 #51

See

Requesting permissions to contribute to Apache Kafka

Hi Team, I am writing this email to request permissions to contribute to Apache Kafka. Here are my details - JIRA ID - adixitconfluent WIKI ID - adixitconfluent Please let me know if anything is missing. Thanks, Abhinav

[jira] [Created] (KAFKA-16091) Pipeline to run docker build test on a PR

Vedarth Sharma created KAFKA-16091: -- Summary: Pipeline to run docker build test on a PR Key: KAFKA-16091 URL: https://issues.apache.org/jira/browse/KAFKA-16091 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-16090) Refactor call to storage tool from kafka docker wrapper

Vedarth Sharma created KAFKA-16090: -- Summary: Refactor call to storage tool from kafka docker wrapper Key: KAFKA-16090 URL: https://issues.apache.org/jira/browse/KAFKA-16090 Project: Kafka

Re: Apache Kafka 3.7.0 Release

Hi, we have fixed one memory leak in Kafka Streams, but there is still at least one missing in the code. I created https://issues.apache.org/jira/browse/KAFKA-16089 which is a blocker. Cheers, Lucas On Sun, Jan 7, 2024 at 12:05 PM Apoorv Mittal wrote: > > Hi Colin, > Thanks for the response.

[jira] [Created] (KAFKA-16089) Kafka Streams still leaking memory in 3.7

Lucas Brutschy created KAFKA-16089: -- Summary: Kafka Streams still leaking memory in 3.7 Key: KAFKA-16089 URL: https://issues.apache.org/jira/browse/KAFKA-16089 Project: Kafka Issue Type: