[jira] [Created] (KAFKA-17446) Kafka streams stuck in rebalancing

Rohit Bobade created KAFKA-17446: Summary: Kafka streams stuck in rebalancing Key: KAFKA-17446 URL: https://issues.apache.org/jira/browse/KAFKA-17446 Project: Kafka Issue Type: Bug Affect

[jira] [Created] (KAFKA-17445) Kafka streams keeps rebalancing with the following reasons

Rohit Bobade created KAFKA-17445: Summary: Kafka streams keeps rebalancing with the following reasons Key: KAFKA-17445 URL: https://issues.apache.org/jira/browse/KAFKA-17445 Project: Kafka Is

Re: [VOTE] KIP-512: make Record Headers available in onAcknowledgement and onComplete

Hi all, Thanks all. We now have 3 binding +1 votes and no -1 votes. KIP-512 is accepted. I will update the KIP status and contribute a PR soon. Regards, Rich On Thu, Aug 29, 2024 at 10:00 PM Lianet M. wrote: > Hi all, > > I'll re-cast my vote here :) > > +1 (binding) > > Thanks Rich! > > > On

[jira] [Created] (KAFKA-17444) High memory allocation rate for FetchSession.update

jinlong wang created KAFKA-17444: Summary: High memory allocation rate for FetchSession.update Key: KAFKA-17444 URL: https://issues.apache.org/jira/browse/KAFKA-17444 Project: Kafka Issue Ty

Re: New release branch 3.9

Thanks Chia-Ping! Sorry for the noise, everyone else :) > On Aug 29, 2024, at 6:36 PM, Chia-Ping Tsai wrote: > > hi Kirk > > I have updated the fix versions of KAFKA-17335 to include 3.9 > > https://issues.apache.org/jira/browse/KAFKA-17335 > > Best, > Chia-Ping > > Chia-Ping Tsai 於 2024年8

Re: [VOTE] KIP-512: make Record Headers available in onAcknowledgement and onComplete

Hi all, I'll re-cast my vote here :) +1 (binding) Thanks Rich! On Fri, Aug 23, 2024, 10:32 p.m. Chia-Ping Tsai wrote: > +1 (binding) > > On 2024/08/10 17:28:45 "Rich C." wrote: > > Hi all, > > > > After incorporating the feedback received > >

Re: New release branch 3.9

hi Kirk I have updated the fix versions of KAFKA-17335 to include 3.9 https://issues.apache.org/jira/browse/KAFKA-17335 Best, Chia-Ping Chia-Ping Tsai 於 2024年8月30日 週五 上午9:32寫道： > hi Kirk > > KAFKA-17335 is already in 3.9 ( > https://github.com/apache/kafka/commit/a87b501a47a55a1f9038b6c52e31b

Re: New release branch 3.9

hi Kirk KAFKA-17335 is already in 3.9 ( https://github.com/apache/kafka/commit/a87b501a47a55a1f9038b6c52e31b71590c3a80a ) Best, Chia-Ping Kirk True 於 2024年8月30日 週五 上午4:36寫道： > Hi Colin, > > KAFKA-17335 (Lack of default for URL encoding configuration for OAuth > causes NPE) affects the internal

Re: [VOTE] KIP-1065: Add "retry" return-option to ProductionExceptionHandler

+1 (binding) Closing this VOTE as "accepted" with 3 binding +1 from Sophie, Bill, and myself. Thanks a lot! -Matthias On 8/28/24 6:09 PM, Bill Bejeck wrote: +1 (binding) On Wed, Aug 28, 2024 at 8:34 PM Sophie Blee-Goldman wrote: Also : +1 (binding) On Wed, Aug 28, 2024 at 3:48 PM Sop

[jira] [Resolved] (KAFKA-17064) New consumer assign should update assignment in background thread

[ https://issues.apache.org/jira/browse/KAFKA-17064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PoAn Yang resolved KAFKA-17064. --- Resolution: Fixed > New consumer assign should update assignment in background thread >

[jira] [Resolved] (KAFKA-17377) Consider using defaultApiTimeoutMs in AsyncKafkaConsumer#unsubscribe

[ https://issues.apache.org/jira/browse/KAFKA-17377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PoAn Yang resolved KAFKA-17377. --- Fix Version/s: 4.0.0 Resolution: Fixed > Consider using defaultApiTimeoutMs in AsyncKafkaCons

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

See

Re: New release branch 3.9

Hi Colin, KAFKA-17335 (Lack of default for URL encoding configuration for OAuth causes NPE) affects the internal use of the OAuth-based AuthenticateCallbackHandler. Can we back port the fix (https://github.com/apache/kafka/pull/16990) to the 3.9 branch? Thanks, Kirk > On Aug 29, 2024, at 11:2

Re: [PR] MINOR: add lianetm to committers [kafka-site]

lianetm merged PR #628: URL: https://github.com/apache/kafka-site/pull/628 -- 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: dev-unsubscr...@kafka.apache.

[jira] [Resolved] (KAFKA-17434) upgrade_test.py tests impossible upgrade scenarios

[ https://issues.apache.org/jira/browse/KAFKA-17434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-17434. -- Fix Version/s: 3.9.0 Resolution: Fixed > upgrade_test.py tests impossible upgrade scena

[PR] MINOR: add lianetm to committers [kafka-site]

lianetm opened a new pull request, #628: URL: https://github.com/apache/kafka-site/pull/628 https://github.com/user-attachments/assets/49f831a1-7d2a-408d-843f-56fa1cf26178";> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

Re: [DISCUSS] KIP-1086: Add ability to specify a custom produce request parser.

I totally understand the burden of maintaining features going forward. The backward compatibility breaking behavior you are describing is a normal part of software evolution, just like deprecation. The potential for having to break backward compatibility sometime in the future is hardly a reason

Re: [DISCUSS] KIP-1086: Add ability to specify a custom produce request parser.

Hi Maxim, The issue is not the number of lines of code, but the need to support this indefinitely in the future. For example, if we want to move to a new request type that is different than ProduceRequest, or create a new version of ProduceRequest, we wouldn't be able to do that in the future w

Re: New release branch 3.9

Hi all, Code freeze has officially arrived for Apache Kafka 3.9! If you have additional fixes to get into the branch at this point, please ping me first (unless it's already marked as a blocker in JIRA). I did a first pass on the list of open JIRAs for 3.9, and moved out any that were not bloc

Re: [DISCUSS] KIP-1086: Add ability to specify a custom produce request parser.

Hi Colin, Thank you for the background. As a new user of Kafka I appreciate being caught up. I tried looking for this in PRs and KIPs but did not find any references. Since my change is tiny, doesn't really change the way the broker works, and only adds an ability to customize the broker without

Re: [DISCUSS] KIP-1086: Add ability to specify a custom produce request parser.

Hi Maxim, Server-side interceptors for messages have been discussed several times, but the KIP never got accepted. People often pushed back on what they saw as the risks and performance problems of allowing user-supplied code in the hot path of accepting records. Your KIP is a bit different be

Re: [DISCUSS] `unclean.leader.election.enable` in KRaft behavior change

Thanks, Luke. Both the static and dynamic options for configuring unclean leader election now work in 3.9, thanks to your help. Dima, if you have only a transient need to do an unclean leader election, using the kafka-leader-election.sh script is still the best way. It avoids the risk for forge

Re: [VOTE] KIP-1042: Support for wildcard when creating new acls

On Thu, Aug 29, 2024, at 01:34, Claude Warren, Jr wrote: > Colin, > > Thanks for your insightful comments. I came to the same conclusion. > > I do have 2 Jira tickets to simplify some of this. > > 1) KAFKA-17316 - Makes > developing a new Au

[jira] [Resolved] (KAFKA-12670) KRaft support for unclean.leader.election.enable

[ https://issues.apache.org/jira/browse/KAFKA-12670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-12670. -- Reviewer: Luke Chen Assignee: Colin McCabe (was: Luke Chen) Resolution: Fixed > K

Re: [DISCUSS] KIP-1082: Enable ID Generation for Clients over the ConsumerGroupHeartbeat RPC

Hi TengYao! Sorry for being late to the discussion... After reading the thread and then the KIP, I had a few questions/comments: KT1: In Motivation, it states: "This scenario can result in the broker registering a new member for which it will never receive a proper leave request.” Just to be c

Re: [DISCUSS] KIP-1086: Add ability to specify a custom produce request parser.

Oooh! All great questions! Answering inline. > On Aug 29, 2024, at 12:00 PM, Kirk True wrote: > > Hi Maxim, > > Thanks for the KIP! > > This is not my area, but I have some questions/comments: > > 1. CMIIW, but I believe that specifying this custom parser class should be > done via configura

[jira] [Resolved] (KAFKA-17390) Remove broker-list in GetOffsetShell

[ https://issues.apache.org/jira/browse/KAFKA-17390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17390. Fix Version/s: 4.0.0 Resolution: Fixed > Remove broker-list in GetOffsetShell > ---

Re: [DISCUSS] KIP-1086: Add ability to specify a custom produce request parser.

Hi Maxim, Thanks for the KIP! This is not my area, but I have some questions/comments: 1. CMIIW, but I believe that specifying this custom parser class should be done via configuration, not system properties or environment variables, right? 2. What happens if the custom parser can’t be loaded?

[jira] [Created] (KAFKA-17443) Create a tool to manipulate share-group state snapshots for recovery purposes

Andrew Schofield created KAFKA-17443: Summary: Create a tool to manipulate share-group state snapshots for recovery purposes Key: KAFKA-17443 URL: https://issues.apache.org/jira/browse/KAFKA-17443

[DISCUSS] KIP-1086: Add ability to specify a custom produce request parser.

Hi all, I would like to introduce a minor code change to allow custom produce request parsers. KIP: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606528 JIRA: https://issues.apache.org/jira/browse/KAFKA-17348 PR: https://github.com/apache/kafka/pull/16812 There are many po

Re: Can't create a KIP

I am now able to create a draft. Thank you, Max > On Aug 29, 2024, at 9:00 AM, Maxim Fortun wrote: > > Ah, right :) I should have started with that :) > Username: maxfortun > Thank you! > > >> On Aug 29, 2024, at 8:58 AM, Bill Bejeck wrote: >> >> Hi Max, >> >> If can share your username,

Re: Can't create a KIP

Max, give it a try now, you should be all set. -Bill On Thu, Aug 29, 2024 at 9:02 AM Maxim Fortun wrote: > Ah, right :) I should have started with that :) > Username: maxfortun > Thank you! > > > > On Aug 29, 2024, at 8:58 AM, Bill Bejeck wrote: > > > > Hi Max, > > > > If can share your userna

Re: [VOTE] KIP-1075: Introduce delayed remote list offsets purgatory to make LIST_OFFSETS async

Hi all, The vote is closed. The KIP has been accepted with 4 +1 binding votes (Satish, Luke, Christo, and Chia-Ping). Thank you all for the participation! -- Kamal On Thu, Aug 29, 2024 at 5:14 PM Chia-Ping Tsai wrote: > +1 (binding) > > On 2024/08/19 05:09:27 Kamal Chandraprakash wrote: > > H

Re: Can't create a KIP

Ah, right :) I should have started with that :) Username: maxfortun Thank you! > On Aug 29, 2024, at 8:58 AM, Bill Bejeck wrote: > > Hi Max, > > If can share your username, and I'll set up your permissions. > > Thanks, > Bill > > On Thu, Aug 29, 2024 at 8:51 AM Maxim Fortun

Re: Can't create a KIP

Hi Max, If can share your username, and I'll set up your permissions. Thanks, Bill On Thu, Aug 29, 2024 at 8:51 AM Maxim Fortun wrote: > Hi, > I created a new wiki account via selfserve yesterday, logged into wiki and > tried to create a KIP, but something doesn't quite seem to connect. > When

Can't create a KIP

Hi, I created a new wiki account via selfserve yesterday, logged into wiki and tried to create a KIP, but something doesn't quite seem to connect. When I hover over "Create KIP" there is a popup that says that I do not have permissions to create content. When I click it, it yields 404. Screensh

Re: [ANNOUNCE] New committer: Lianet Magrans

Congratulations, Lianet! Regards, Rajini On Thu, Aug 29, 2024 at 7:57 AM Kuan Po Tseng wrote: > Congrats Lianet !!! > > On 2024/08/29 02:37:19 Luke Chen wrote: > > Congratulations Lianet! > > > > Luke > > > > On Thu, Aug 29, 2024 at 9:54 AM Lianet M. wrote: > > > > > Thank you very much every

[jira] [Resolved] (KAFKA-17388) Remove broker-list in VerifiableProducer

[ https://issues.apache.org/jira/browse/KAFKA-17388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17388. Fix Version/s: 4.0.0 Resolution: Fixed > Remove broker-list in VerifiableProducer >

Re: [VOTE] KIP-1075: Introduce delayed remote list offsets purgatory to make LIST_OFFSETS async

+1 (binding) On 2024/08/19 05:09:27 Kamal Chandraprakash wrote: > Hi, > > I would like to open voting for KIP-1075. I've addressed the review > comments in the discussion thread. Please vote if the proposal looks good. > > https://cwiki.apache.org/confluence/plugins/servlet/mobile?contentId=3154

Re: [DISCUSS] KIP-1075: Introduce delayed remote list offsets purgatory to make LIST_OFFSETS async

Hi Chia-Ping, Thanks for the review! This is a good point to add provision to convey the timeout from client to the server. Updated the KIP to add a new 'TimeoutMs' field in the ListOffsetsRequest and bumped the version to 10. To retain the existing ListOffsets request behaviour: 1. AdminClient

[jira] [Resolved] (KAFKA-17396) Fix releasing of session on clients final epoch

[ https://issues.apache.org/jira/browse/KAFKA-17396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-17396. --- Resolution: Fixed > Fix releasing of session on clients final epoch > --

[jira] [Created] (KAFKA-17442) Implement persister error handling and make write calls async

Apoorv Mittal created KAFKA-17442: - Summary: Implement persister error handling and make write calls async Key: KAFKA-17442 URL: https://issues.apache.org/jira/browse/KAFKA-17442 Project: Kafka

[jira] [Resolved] (KAFKA-17283) Add integration test for Share Group heartbeat

[ https://issues.apache.org/jira/browse/KAFKA-17283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-17283. --- Resolution: Fixed > Add integration test for Share Group heartbeat > ---

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.9 #50

See

Re: [VOTE] KIP-1042: Support for wildcard when creating new acls

Colin, Thanks for your insightful comments. I came to the same conclusion. I do have 2 Jira tickets to simplify some of this. 1) KAFKA-17316 - Makes developing a new Authorizer by creating a new implementation of the StandardAuthorizerData ea

Re: [DISCUSS] KIP-1082: Enable ID Generation for Clients over the ConsumerGroupHeartbeat RPC

Hi David, Thank you for pointing that out. I have updated the content of the KIP based on Lianet's and your feedback. Please take a look and let me know your thoughts. Best regards, TengYao David Jacot 於 2024年8月29日 週四 下午3:20寫道： > Hi TengYao, > > Thanks for the update. I haven't fully read it y

[jira] [Resolved] (KAFKA-17413) Re-introduce `group.version` feature flag

[ https://issues.apache.org/jira/browse/KAFKA-17413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-17413. - Resolution: Fixed > Re-introduce `group.version` feature flag >

Re: Permissions to create or update KIPs

Hi Loic, Thanks for your interest in Apache Kafka! Your accounts are all set up. Let me know if you have any problems! Best, On Thu, Aug 29, 2024 at 10:04 AM Loic Greffier wrote: > Hello, > > I would like to have permissions to create or update KIPs. > > My Confluence ID and Jira ID are "loicg

Permissions to create or update KIPs

Hello, I would like to have permissions to create or update KIPs. My Confluence ID and Jira ID are "loicgreffier" for both. Thanks!

Re: [DISCUSS] KIP-1082: Enable ID Generation for Clients over the ConsumerGroupHeartbeat RPC

Hi TengYao, Thanks for the update. I haven't fully read it yet but I will soon. LM4: This is incorrect. The consumer must keep its member id during its entire lifetime (until the process stops or dies). The protocol stipulates that a member must rejoin with the same member id and the member epoch