Re: [DISCUSS] KIP-953: partition method to be overloaded to accept headers as well.

Hi Jack, Thanks for the KIP! Seems like an interesting idea. I have some feedback: 1) It would be great if you could clean up the text that seems to mimic the KIP template. It is generally not required in the KIP. 2) In the Public Interfaces where you mentioned *Partitioner method in

[GitHub] [kafka-site] mjsax commented on pull request #528: MINOR: Add statmenet about ZK deprecation to 3.5 release blog post

mjsax commented on PR #528: URL: https://github.com/apache/kafka-site/pull/528#issuecomment-1639047530 We got a PR for the ZK section: https://github.com/apache/kafka/pull/14031 In case you want to take a look. -- This is an automated message from the Apache Git Service. To respond

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

See Changes: -- [...truncated 387636 lines...] Gradle Test Run :streams:integrationTest > Gradle Test Executor 182 > RestoreIntegrationTest >

Re: [VOTE] 3.5.1 RC1

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

[jira] [Created] (KAFKA-15202) MM2 OffsetSyncStore clears too many syncs when sync spacing is variable

Greg Harris created KAFKA-15202: --- Summary: MM2 OffsetSyncStore clears too many syncs when sync spacing is variable Key: KAFKA-15202 URL: https://issues.apache.org/jira/browse/KAFKA-15202 Project: Kafka

[jira] [Created] (KAFKA-15201) When git fails, script goes into a loop

Divij Vaidya created KAFKA-15201: Summary: When git fails, script goes into a loop Key: KAFKA-15201 URL: https://issues.apache.org/jira/browse/KAFKA-15201 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-15200) verify pre-requisite at start of release.py

Divij Vaidya created KAFKA-15200: Summary: verify pre-requisite at start of release.py Key: KAFKA-15200 URL: https://issues.apache.org/jira/browse/KAFKA-15200 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-15199) remove leading and trailing spaces from user input in release.py

Divij Vaidya created KAFKA-15199: Summary: remove leading and trailing spaces from user input in release.py Key: KAFKA-15199 URL: https://issues.apache.org/jira/browse/KAFKA-15199 Project: Kafka

[jira] [Created] (KAFKA-15198) Improve version release scripts

Divij Vaidya created KAFKA-15198: Summary: Improve version release scripts Key: KAFKA-15198 URL: https://issues.apache.org/jira/browse/KAFKA-15198 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-15197) Flaky test MirrorConnectorsIntegrationExactlyOnceTest.testOffsetTranslationBehindReplicationFlow()

Divij Vaidya created KAFKA-15197: Summary: Flaky test MirrorConnectorsIntegrationExactlyOnceTest.testOffsetTranslationBehindReplicationFlow() Key: KAFKA-15197 URL:

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

See

[jira] [Created] (KAFKA-15196) Additional ZK migration metrics

David Arthur created KAFKA-15196: Summary: Additional ZK migration metrics Key: KAFKA-15196 URL: https://issues.apache.org/jira/browse/KAFKA-15196 Project: Kafka Issue Type: Sub-task

Re: [DISCUSS] KIP-951: Leader discovery optimisations for the client

Hey Mayank: For #1: I think fetch and produce behave a bit differently on metadata. Maybe it is worth highlighting the changes for each client in detail. In producer did you mean by the metadata timeout before sending out produce requests? For consumer: I think for fetches it requires user to

Re: [DISCUSS] KIP-951: Leader discovery optimisations for the client

Philip 1. Good call out about "poll" behaviour, my understanding is the same. I am assuming it's about the motivation of the KIP. There with async, my intention was to convey that the client doesn't wait for the metadata-refresh before a subsequent retry of the produce or fetch request that

Re: [DISCUSS] KIP-951: Leader discovery optimisations for the client

Kirk 1. For the client, it doesn't matter whether the server is KRaft or ZK. Client behaviour will be simply driven by the protocol-changes proposed for the FetchResponse & ProduceResponse. On the server side, there will be differences on how a new leader is discovered depending on whether it's

[jira] [Resolved] (KAFKA-14884) Include check transaction is still ongoing right before append

[ https://issues.apache.org/jira/browse/KAFKA-14884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-14884. Resolution: Fixed > Include check transaction is still ongoing right before append >

[jira] [Resolved] (KAFKA-15193) Allow choosing Platform specific rocksDBJNI jar

[ https://issues.apache.org/jira/browse/KAFKA-15193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Utkarsh Khare resolved KAFKA-15193. --- Resolution: Not A Problem > Allow choosing Platform specific rocksDBJNI jar >

Re: [VOTE] 3.5.1 RC1

Hi Divij, I did the following checks: - Checked signature, checksum, licenses - Spot checked documentation and javadoc - Built from source with Java 17 and Scala 2.13 - Ran full unit and integration test suites - Ran test Java app using staging Maven artifacts +1 (non binding) Cheers Fede On

[DISCUSS] KIP-952: Regenerate segment-aligned producer snapshots when upgrading to a Kafka version supporting Tiered Storage

Hello! A customer upgrading from Kafka < 2.8 to the future release 3.6 and wanting to enable tiered storage would have to take responsibility for ensuring that all segments lacking a producer snapshot file have expired and are deleted before enabling the feature. In our experience customers are

Re: [DISCUSS] KIP-953: partition method to be overloaded to accept headers as well.

Hey everyone, Not seeing much discussion on the KPI. Might be because it is too obvious . If there are no more comments, I will start the VOTE in the coming days. On Sat, Jul 15, 2023 at 8:48 PM Jack Tomy wrote: > Hey everyone, > > Please take a look at the KPI below and provide your

[jira] [Created] (KAFKA-15195) Regenerate segment-aligned producer snapshots when upgrading to a Kafka version supporting Tiered Storage

Christo Lolov created KAFKA-15195: - Summary: Regenerate segment-aligned producer snapshots when upgrading to a Kafka version supporting Tiered Storage Key: KAFKA-15195 URL:

Re: [DISCUSS] KIP-951: Leader discovery optimisations for the client

Hi Krik, On Fri, Jul 14, 2023 at 10:59 AM Kirk True wrote: > Is the requested restructuring of the response “simply” to preserve bytes, or > is it possible that the fetch response could/should/would return leadership > changes for partitions that we’re specifically requested? Both. My

Re: Re: [DISCUSS] KIP-951: Leader discovery optimisations for the client

Emanuele I agree with this. That's why i quoted below - > I wonder if non-Kafka clients might benefit from not bumping the > version. If versions are bumped, say for FetchResponse to 16, I believe > that client would have to support all versions until 16 to fully > utilise this feature. Whereas,

Re: [DISCUSS] KIP-714: Client metrics and observability

Hi Andrew, thanks for this KIP. I had a few questions regarding the "Error handling" section. 1. It mentions that "The 5 and 30 minute retries are to eventually trigger a retry and avoid having to restart clients if the cluster metrics configuration is disabled temporarily, e.g., by operator

[jira] [Created] (KAFKA-15194) Rename local tiered storage segment with offset as prefix for easy navigation

Kamal Chandraprakash created KAFKA-15194: Summary: Rename local tiered storage segment with offset as prefix for easy navigation Key: KAFKA-15194 URL: https://issues.apache.org/jira/browse/KAFKA-15194

RE: Re: [DISCUSS] KIP-951: Leader discovery optimisations for the client

The downsides of bumping the version is that clients have to have all the latest features implemented before being able to benefit from this performance improvement. One of the benefits of using a tagged field is to make the field available to previous versions too. Choosing a minimum value

[jira] [Resolved] (KAFKA-14518) Rebalance on topic/partition metadata changes

[ https://issues.apache.org/jira/browse/KAFKA-14518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-14518. - Resolution: Fixed This was done as part of https://issues.apache.org/jira/browse/KAFKA-14462.

[jira] [Created] (KAFKA-15193) Allow choosing Platform specific rocksDBJNI jar

Utkarsh Khare created KAFKA-15193: - Summary: Allow choosing Platform specific rocksDBJNI jar Key: KAFKA-15193 URL: https://issues.apache.org/jira/browse/KAFKA-15193 Project: Kafka Issue

Re: Application for permission grants for contribution

Hi Abhinav, You should be all set now. Thanks for your interest in Apache Kafka! Best, Bruno On 7/14/23 9:04 AM, abhinav tripathi wrote: Hi Team, I would like to contribute to the Kafka community. I want to work on open issues and also have some ideas of my own. Requesting access and grants

Re: Requesting permissions to contribute to Apache Kafka

Hi Mital, You should be all set now. Thanks for your interest in Apache Kafka! Best, Bruno On 7/14/23 3:04 PM, Mital Awachat wrote: Hi Team, I am requesting permission to contribute to Apache Kafka. Wiki: Username: mital.awachat Email: mital.awacha...@gmail.com Jira: Username:

[VOTE] 3.5.1 RC1

Hello Kafka users, developers and client-developers, This is the second candidate (RC1) for release of Apache Kafka 3.5.1. First release candidate (RC0) was discarded due to incorrect license files. They have been fixed since then. This release is a security patch release. It upgrades the

Re: [VOTE] 3.5.1 RC0

Please ignore this. I need to re-send this email with the correct release canddiate in this email. -- Divij Vaidya On Mon, Jul 17, 2023 at 10:07 AM Divij Vaidya wrote: > Hello Kafka users, developers and client-developers, > > This is the second candidate (RC1) for release of Apache Kafka

[VOTE] 3.5.1 RC0

Hello Kafka users, developers and client-developers, This is the second candidate (RC1) for release of Apache Kafka 3.5.1. First release candidate (RC0) was discarded due to incorrect license files. They have been fixed since then. This release is a security patch release. It upgrades the