[jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19472: Description: RemoteLogReader throws a BufferOverflowException when FetchApi version <= 2 and firs

[jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19472: Description: RemoteLogReader throws a BufferOverflowException when FetchApi version <= 2 and firs

[jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19472: Attachment: screenshot-1.png > A BufferOverflowException is thrown by RemoteLogManager when FetchA

[jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19472: Description: RemoteLogReader throws a BufferOverflowException when FetchApi version <= 2 and firs

[jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19473: Attachment: (was: screenshot-1.png) > The client does not throw RecordTooLargeException when t

[jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19473: Description: When the Record size is greater than max.partition.fetch.bytes, the client does  not 

[jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19473: Attachment: screenshot-2.png > The client does not throw RecordTooLargeException when the Record s

[jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19473: Description: When the Record size is greater than max.partition.fetch.bytes, the client does  not 

[jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19473: Description: When the Record size is greater than max.partition.fetch.bytes, the client does  not 

[jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19473: Description: When the Record size is greater than max.partition.fetch.bytes, the client does  not 

[jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19473: Attachment: screenshot-1.png > The client does not throw RecordTooLargeException when the Record s

Re: [PR] KAFKA 18238 - fIdentify the first commit where a test became flaky [kafka]

2025-07-04 Thread via GitHub
github-actions[bot] commented on PR #18334: URL: https://github.com/apache/kafka/pull/18334#issuecomment-3037855129 This PR is being marked as stale since it has not had any activity in 90 days. If you would like to keep this PR alive, please leave a comment asking for a review. If the P

Re: [PR] Bug fixes for delete and state epoch. [kafka]

2025-07-04 Thread via GitHub
github-actions[bot] commented on PR #20056: URL: https://github.com/apache/kafka/pull/20056#issuecomment-3037840227 A label of 'needs-attention' was automatically added to this PR in order to raise the attention of the committers. Once this issue has been triaged, the `triage` label s

Re: [PR] KAFKA-19443: test-common ClusterInstance should make it easy to have more listeners [kafka]

2025-07-04 Thread via GitHub
github-actions[bot] commented on PR #20057: URL: https://github.com/apache/kafka/pull/20057#issuecomment-3037840214 A label of 'needs-attention' was automatically added to this PR in order to raise the attention of the committers. Once this issue has been triaged, the `triage` label s

Re: [PR] MINOR: Move ClientQuotasRequestTest to server module [kafka]

2025-07-04 Thread via GitHub
DL1231 commented on code in PR #20053: URL: https://github.com/apache/kafka/pull/20053#discussion_r2186397427 ## server/src/test/java/org/apache/kafka/server/quota/ClientQuotasRequestTest.java: ## @@ -0,0 +1,720 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under o

Re: [PR] KAFKA-19431: Ensure consumer and share assignment consistency with subscriptions [kafka]

2025-07-04 Thread via GitHub
lianetm commented on code in PR #20055: URL: https://github.com/apache/kafka/pull/20055#discussion_r2186107711 ## group-coordinator/src/main/java/org/apache/kafka/coordinator/group/modern/consumer/CurrentAssignmentBuilder.java: ## @@ -317,4 +451,29 @@ private ConsumerGroupMember

[jira] [Updated] (KAFKA-18035) TransactionsTest testBumpTransactionalEpochWithTV2Disabled failed on trunk

2025-07-04 Thread Chia-Ping Tsai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated KAFKA-18035: --- Fix Version/s: 4.0.1 > TransactionsTest testBumpTransactionalEpochWithTV2Disabled failed on

Re: [PR] KAFKA-19221: Backport to 4.0 [kafka]

2025-07-04 Thread via GitHub
chia7712 commented on PR #20072: URL: https://github.com/apache/kafka/pull/20072#issuecomment-3037235188 @gaurav-narula could you please sync 4.0 to trigger QA again? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use th

Re: [PR] KAFKA-19397: Ensure consistent metadata usage in produce request and response [kafka]

2025-07-04 Thread via GitHub
chia7712 commented on PR #19964: URL: https://github.com/apache/kafka/pull/19964#issuecomment-3037235784 @OmniaGM could you please backport it to 4.1 branch? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abo

Re: [PR] KAFKA-18035: Backport TransactionsTest testBumpTransactionalEpochWithTV2Disabled failed on trunk [kafka]

2025-07-04 Thread via GitHub
chia7712 merged PR #20102: URL: https://github.com/apache/kafka/pull/20102 -- 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: jira-unsubscr...@kafka.apache

Re: [PR] KAFKA-19431: Ensure consumer and share assignment consistency with subscriptions [kafka]

2025-07-04 Thread via GitHub
squah-confluent commented on code in PR #20055: URL: https://github.com/apache/kafka/pull/20055#discussion_r2186077989 ## group-coordinator/src/main/java/org/apache/kafka/coordinator/group/GroupMetadataManager.java: ## @@ -2243,21 +2243,30 @@ private CoordinatorResult

Re: [PR] KAFKA-19301: Move and rewrite partition state classes to Java in org.apache.kafka.storage.internals.log [kafka]

2025-07-04 Thread via GitHub
chia7712 commented on code in PR #20083: URL: https://github.com/apache/kafka/pull/20083#discussion_r2185863531 ## storage/src/main/java/org/apache/kafka/storage/internals/log/CommittedPartitionState.java: ## @@ -0,0 +1,41 @@ +/* + * Licensed to the Apache Software Foundation (A

Re: [PR] MINOR: Move ClientQuotasRequestTest to server module [kafka]

2025-07-04 Thread via GitHub
Yunyung commented on code in PR #20053: URL: https://github.com/apache/kafka/pull/20053#discussion_r2185757102 ## server/src/test/java/org/apache/kafka/server/quota/ClientQuotasRequestTest.java: ## @@ -0,0 +1,720 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under

Re: [PR] MINOR: Move ClientQuotasRequestTest to server module [kafka]

2025-07-04 Thread via GitHub
Yunyung commented on code in PR #20053: URL: https://github.com/apache/kafka/pull/20053#discussion_r2185757102 ## server/src/test/java/org/apache/kafka/server/quota/ClientQuotasRequestTest.java: ## @@ -0,0 +1,720 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under

Re: [PR] MINOR: Move ClientQuotasRequestTest to server module [kafka]

2025-07-04 Thread via GitHub
Yunyung commented on code in PR #20053: URL: https://github.com/apache/kafka/pull/20053#discussion_r2185757102 ## server/src/test/java/org/apache/kafka/server/quota/ClientQuotasRequestTest.java: ## @@ -0,0 +1,720 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under

Re: [PR] KAFKA-19315: Move ControllerMutationQuotaManager to server module [kafka]

2025-07-04 Thread via GitHub
chia7712 commented on code in PR #19807: URL: https://github.com/apache/kafka/pull/19807#discussion_r2185851333 ## server/src/main/java/org/apache/kafka/server/ClientQuotaManager.java: ## @@ -0,0 +1,908 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or mor

Re: [PR] KAFKA-19315: Move ControllerMutationQuotaManager to server module [kafka]

2025-07-04 Thread via GitHub
chia7712 commented on code in PR #19807: URL: https://github.com/apache/kafka/pull/19807#discussion_r2185784855 ## server/src/main/java/org/apache/kafka/server/ClientQuotaManager.java: ## @@ -0,0 +1,908 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or mor

[jira] [Updated] (KAFKA-19474) Wrong placement of WARN log for truncation below HWM

2025-07-04 Thread Gaurav Narula (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Narula updated KAFKA-19474: -- Affects Version/s: (was: 4.2.0) > Wrong placement of WARN log for truncation below HWM > -

[jira] [Updated] (KAFKA-19474) Wrong placement of WARN log for truncation below HWM

2025-07-04 Thread Gaurav Narula (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Narula updated KAFKA-19474: -- Affects Version/s: 4.1.0 > Wrong placement of WARN log for truncation below HWM >

[jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19473: Attachment: image-2025-07-05-00-54-23-657.png > The client does not throw RecordTooLargeException

[jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19473: Description: When the Record size is greater than max.partition.fetch.bytes, the client does  not 

Re: [PR] KAFKA-19397: Ensure consistent metadata usage in produce request and response [kafka]

2025-07-04 Thread via GitHub
OmniaGM commented on PR #19964: URL: https://github.com/apache/kafka/pull/19964#issuecomment-3036879000 > @OmniaGM thanks for handling that crisis. BTW, we have a commit tool https://github.com/apache/kafka/blob/trunk/committer-tools/reviewers.py which can easily add `reviewers` to the comm

[jira] [Updated] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19473: Attachment: 20250705-005334.jpeg > The client does not throw RecordTooLargeException when the Reco

Re: [PR] KAFKA-19474: Move WARN log on log truncation below HWM [kafka]

2025-07-04 Thread via GitHub
gaurav-narula commented on PR #20106: URL: https://github.com/apache/kafka/pull/20106#issuecomment-3036877668 CC: @hachikuji @junrao can you please take a look. This is related to https://github.com/apache/kafka/pull/5608 -- This is an automated message from the Apache Git Service. To res

Re: [PR] KAFKA-19397: Ensure consistent metadata usage in produce request and response [kafka]

2025-07-04 Thread via GitHub
chia7712 commented on PR #19964: URL: https://github.com/apache/kafka/pull/19964#issuecomment-3036876302 @OmniaGM thanks for handling that crisis. BTW, we have a commit tool https://github.com/apache/kafka/blob/trunk/committer-tools/reviewers.py which can easily add `reviewers` to the commi

Re: [PR] MINOR: Cleanups in ConfigurationUtils [kafka]

2025-07-04 Thread via GitHub
ThibaudAV commented on code in PR #18576: URL: https://github.com/apache/kafka/pull/18576#discussion_r2185778322 ## clients/src/main/java/org/apache/kafka/common/security/oauthbearer/internals/secured/ConfigurationUtils.java: ## @@ -228,4 +233,21 @@ public T get(String name) {

Re: [PR] MINOR: Cleanups in ConfigurationUtils [kafka]

2025-07-04 Thread via GitHub
ThibaudAV commented on code in PR #18576: URL: https://github.com/apache/kafka/pull/18576#discussion_r2185778322 ## clients/src/main/java/org/apache/kafka/common/security/oauthbearer/internals/secured/ConfigurationUtils.java: ## @@ -228,4 +233,21 @@ public T get(String name) {

[PR] KAFKA-19474: Move WARN log on log truncation below HWM [kafka]

2025-07-04 Thread via GitHub
gaurav-narula opened a new pull request, #20106: URL: https://github.com/apache/kafka/pull/20106 Moves the check for `offsetTruncationState.offset < log.highWatermark` before truncating the log as truncation might update the HWM thereby leading to an incorrect condition evaluation. --

Re: [PR] KAFKA-19397: Ensure consistent metadata usage in produce request and response [kafka]

2025-07-04 Thread via GitHub
OmniaGM merged PR #19964: URL: https://github.com/apache/kafka/pull/19964 -- 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: jira-unsubscr...@kafka.apache.

Re: [PR] KAFKA-19397: Ensure consistent metadata usage in produce request and response [kafka]

2025-07-04 Thread via GitHub
junrao commented on PR #19964: URL: https://github.com/apache/kafka/pull/19964#issuecomment-3036856692 I ran an existing test `testSendWithTopicReassignmentIsMidWay` until failure and hit the same failure ([test_failure2.txt](https://github.com/user-attachments/files/21062667/test_failu

[jira] [Updated] (KAFKA-19474) Wrong placement of WARN log for truncation below HWM

2025-07-04 Thread Gaurav Narula (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Narula updated KAFKA-19474: -- Affects Version/s: 2.1.0 > Wrong placement of WARN log for truncation below HWM >

[jira] [Assigned] (KAFKA-19474) Wrong placement of WARN log for truncation below HWM

2025-07-04 Thread Gaurav Narula (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gaurav Narula reassigned KAFKA-19474: - Assignee: Gaurav Narula > Wrong placement of WARN log for truncation below HWM > --

[jira] [Created] (KAFKA-19474) Wrong placement of WARN log for truncation below HWM

2025-07-04 Thread Gaurav Narula (Jira)
Gaurav Narula created KAFKA-19474: - Summary: Wrong placement of WARN log for truncation below HWM Key: KAFKA-19474 URL: https://issues.apache.org/jira/browse/KAFKA-19474 Project: Kafka Issue

Re: [PR] MINOR: Move ClientQuotasRequestTest to server module [kafka]

2025-07-04 Thread via GitHub
Yunyung commented on code in PR #20053: URL: https://github.com/apache/kafka/pull/20053#discussion_r2185757102 ## server/src/test/java/org/apache/kafka/server/quota/ClientQuotasRequestTest.java: ## @@ -0,0 +1,720 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under

[jira] [Created] (KAFKA-19473) The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes

2025-07-04 Thread dyingjiecai (Jira)
dyingjiecai created KAFKA-19473: --- Summary: The client does not throw RecordTooLargeException when the Record size exceeds max.partition.fetch.bytes Key: KAFKA-19473 URL: https://issues.apache.org/jira/browse/KAFKA-1

[jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19472: Environment: BrokerVersion 3.9.1 ClientVersion 0.10.0.0 Client max.partitioin.fetch.bytes > record

[jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19472: Affects Version/s: 3.9.1 (was: 3.9.0) > A BufferOverflowException is th

[jira] [Updated] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2

2025-07-04 Thread dyingjiecai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dyingjiecai updated KAFKA-19472: Description: RemoteLogReader throws a BufferOverflowException when FetchApi version <= 2 and firs

[jira] [Created] (KAFKA-19472) A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2

2025-07-04 Thread dyingjiecai (Jira)
dyingjiecai created KAFKA-19472: --- Summary: A BufferOverflowException is thrown by RemoteLogManager when FetchApiVersion <= 2 Key: KAFKA-19472 URL: https://issues.apache.org/jira/browse/KAFKA-19472 Proje

Re: [PR] KAFKA-19306: Migrate LogCompactionTester to tools module [kafka]

2025-07-04 Thread via GitHub
chia7712 commented on code in PR #19905: URL: https://github.com/apache/kafka/pull/19905#discussion_r2185713800 ## tools/src/main/java/org/apache/kafka/tools/TestRecord.java: ## @@ -0,0 +1,73 @@ +/* + * Licensed to the Apache Software Foundation (ASF) under one or more + * contr

Re: [PR] KAFKA-19221: Backport to 4.0 [kafka]

2025-07-04 Thread via GitHub
chia7712 commented on PR #20072: URL: https://github.com/apache/kafka/pull/20072#issuecomment-3036779147 @gaurav-narula I will merge #20102 first -- 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 t

Re: [PR] KAFKA-19042 Move PlaintextConsumerTest to client-integration-tests module [kafka]

2025-07-04 Thread via GitHub
Yunyung commented on code in PR #20081: URL: https://github.com/apache/kafka/pull/20081#discussion_r2185548023 ## core/src/test/scala/integration/kafka/api/PlaintextConsumerTest.scala: ## @@ -1,892 +0,0 @@ -/** - * Licensed to the Apache Software Foundation (ASF) under one or m

[jira] [Commented] (KAFKA-19471) Enable acknowledgement for a record which could not be deserialized

2025-07-04 Thread Lan Ding (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17995778#comment-17995778 ] Lan Ding commented on KAFKA-19471: -- Hi [~schofielaj], if you're not working on this, ma

[jira] [Created] (KAFKA-19471) Enable acknowledgement for a record which could not be deserialized

2025-07-04 Thread Andrew Schofield (Jira)
Andrew Schofield created KAFKA-19471: Summary: Enable acknowledgement for a record which could not be deserialized Key: KAFKA-19471 URL: https://issues.apache.org/jira/browse/KAFKA-19471 Project:

Re: [PR] KAFKA-19397: Ensure consistent metadata usage in produce request and response [kafka]

2025-07-04 Thread via GitHub
OmniaGM commented on PR #19964: URL: https://github.com/apache/kafka/pull/19964#issuecomment-3036595933 > [test_failure.txt](https://github.com/user-attachments/files/21044139/test_failure.txt) > > > > @chia7712 : Attached is the test failure output. It still happened after t

Re: [PR] KAFKA-18149: Docs improvement for dynamic kraft quorum [kafka]

2025-07-04 Thread via GitHub
FrankYang0529 commented on code in PR #18350: URL: https://github.com/apache/kafka/pull/18350#discussion_r2185514967 ## docs/ops.html: ## @@ -3923,6 +3923,10 @@ bin/kafka-metadata-quorum.sh describe --replication command. Once the new controller has caught up to the active con

[jira] [Resolved] (KAFKA-19468) Share group epoch increments on every heartbeat if subscribed topics removed

2025-07-04 Thread Andrew Schofield (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-19468. -- Resolution: Fixed > Share group epoch increments on every heartbeat if subscribed topi

Re: [PR] KAFKA-19468: Ignore unsubscribed topics when computing share assignment [kafka]

2025-07-04 Thread via GitHub
AndrewJSchofield merged PR #20101: URL: https://github.com/apache/kafka/pull/20101 -- 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: jira-unsubscr...@kafk

Re: [PR] KAFKA-19431: Ensure consumer and share assignment consistency with subscriptions [kafka]

2025-07-04 Thread via GitHub
lianetm commented on code in PR #20055: URL: https://github.com/apache/kafka/pull/20055#discussion_r2185448060 ## group-coordinator/src/main/java/org/apache/kafka/coordinator/group/GroupMetadataManager.java: ## @@ -2243,21 +2243,30 @@ private CoordinatorResult // epoch

Re: [PR] KAFKA-19431: Ensure consumer and share assignment consistency with subscriptions [kafka]

2025-07-04 Thread via GitHub
lianetm commented on code in PR #20055: URL: https://github.com/apache/kafka/pull/20055#discussion_r2185448060 ## group-coordinator/src/main/java/org/apache/kafka/coordinator/group/GroupMetadataManager.java: ## @@ -2243,21 +2243,30 @@ private CoordinatorResult // epoch

Re: [PR] MINOR: Cleanups in coordinator-common/group-coordinator [kafka]

2025-07-04 Thread via GitHub
Yunyung commented on code in PR #20097: URL: https://github.com/apache/kafka/pull/20097#discussion_r2185381222 ## group-coordinator/src/main/java/org/apache/kafka/coordinator/group/streams/TopologyMetadata.java: ## @@ -36,7 +36,7 @@ public record TopologyMetadata(MetadataImage

Re: [PR] KAFKA-14915: allow read remote storage for multiple partitions in one fetchRequest [kafka]

2025-07-04 Thread via GitHub
kamalcph commented on code in PR #20045: URL: https://github.com/apache/kafka/pull/20045#discussion_r2185284298 ## core/src/main/scala/kafka/server/DelayedRemoteFetch.scala: ## @@ -90,8 +92,13 @@ class DelayedRemoteFetch(remoteFetchTask: Future[Void], override def onExpiratio

Re: [PR] KAFKA-18288: Fix Streams CLI describe [kafka]

2025-07-04 Thread via GitHub
aliehsaeedii commented on code in PR #20099: URL: https://github.com/apache/kafka/pull/20099#discussion_r2185252318 ## clients/src/main/java/org/apache/kafka/clients/admin/internals/DescribeStreamsGroupsHandler.java: ## @@ -259,22 +258,9 @@ private void handleError(

Re: [PR] KAFKA-19470 Avoid creating loggers repeatedly to affect the performance of request processing [kafka]

2025-07-04 Thread via GitHub
terrytlu commented on PR #20105: URL: https://github.com/apache/kafka/pull/20105#issuecomment-3035977850 hello @ijuma @divijvaidya , could please help review this pr 🙏 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use t

Re: [PR] KAFKA-18288: Fix Streams CLI describe [kafka]

2025-07-04 Thread via GitHub
lucasbru commented on code in PR #20099: URL: https://github.com/apache/kafka/pull/20099#discussion_r2185194293 ## clients/src/main/java/org/apache/kafka/clients/admin/internals/DescribeStreamsGroupsHandler.java: ## @@ -259,22 +258,9 @@ private void handleError(

Re: [PR] KAFKA-18288: Fix Streams CLI describe [kafka]

2025-07-04 Thread via GitHub
Copilot commented on code in PR #20099: URL: https://github.com/apache/kafka/pull/20099#discussion_r2185196020 ## tools/src/test/java/org/apache/kafka/tools/streams/DescribeStreamsGroupTest.java: ## @@ -170,21 +199,87 @@ public void testDescribeStreamsGroupWithMembersAndVerbose

[PR] KAFKA-19470 Avoid creating loggers repeatedly to affect the performance of request processing [kafka]

2025-07-04 Thread via GitHub
terrytlu opened a new pull request, #20105: URL: https://github.com/apache/kafka/pull/20105 fix the issue mentioned https://issues.apache.org/jira/browse/KAFKA-19470, to avoid the jdk11 + lo4j2 performance issue. Optimize the trait Logging, introduce a static Map object to cache the same

Re: [PR] KAFKA-19457: Make share group init retry interval configurable. [kafka]

2025-07-04 Thread via GitHub
AndrewJSchofield commented on code in PR #20104: URL: https://github.com/apache/kafka/pull/20104#discussion_r2185151611 ## group-coordinator/src/main/java/org/apache/kafka/coordinator/group/GroupCoordinatorConfig.java: ## @@ -484,6 +493,9 @@ public GroupCoordinatorConfig(Abstrac

[jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing

2025-07-04 Thread terrytlu (Jira)
gt;Affects Versions: 2.8.2 >Reporter: terrytlu >Priority: Major > Attachments: 20250704-145553.html, image-2025-07-04-19-05-51-900.png, > image-2025-07-04-19-25-57-774.png > > > We see that the broker has a performance bottleneck when processing requests

[jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing

2025-07-04 Thread terrytlu (Jira)
gt;Reporter: terrytlu >Priority: Major > Attachments: 20250704-145553.html, image-2025-07-04-19-05-51-900.png, > image-2025-07-04-19-25-57-774.png > > > We see that the broker has a performance bottleneck when processing requests > in kafka 2.8.2 versio

[jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing

2025-07-04 Thread terrytlu (Jira)
mponents: core >Affects Versions: 2.8.2 >Reporter: terrytlu >Priority: Major > Attachments: 20250704-145553.html, image-2025-07-04-19-05-51-900.png, > image-2025-07-04-19-25-57-774.png > > > We see that the broker has a performance bottleneck

[jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing

2025-07-04 Thread terrytlu (Jira)
Issue Type: Improvement > Components: core >Affects Versions: 2.8.2 >Reporter: terrytlu >Priority: Major > Attachments: 20250704-145553.html, image-2025-07-04-19-05-51-900.png, > image-2025-07-04-19-25-57-774.png > > > We se

[jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing

2025-07-04 Thread terrytlu (Jira)
Issue Type: Improvement > Components: core >Affects Versions: 2.8.2 >Reporter: terrytlu >Priority: Major > Attachments: 20250704-145553.html, image-2025-07-04-19-05-51-900.png, > image-2025-07-04-19-25-57-774.png > > > We see that the

[jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing

2025-07-04 Thread terrytlu (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] terrytlu updated KAFKA-19470: - Attachment: 20250704-145553.html > Avoid creating loggers repeatedly to affect the performance

[jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing

2025-07-04 Thread terrytlu (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] terrytlu updated KAFKA-19470: - Description: We see that the broker has a performance bottleneck when processing requests in kafka 2.8.

[jira] [Updated] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing

2025-07-04 Thread terrytlu (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] terrytlu updated KAFKA-19470: - Description: We see that the broker has a performance bottleneck when processing requests in kafka 2.8.

[jira] [Created] (KAFKA-19470) Avoid creating loggers repeatedly to affect the performance of request processing

2025-07-04 Thread terrytlu (Jira)
terrytlu created KAFKA-19470: Summary: Avoid creating loggers repeatedly to affect the performance of request processing Key: KAFKA-19470 URL: https://issues.apache.org/jira/browse/KAFKA-19470 Project: Ka

[jira] [Resolved] (KAFKA-19363) Enhance share group assignor for heterogeneous subscription type

2025-07-04 Thread Andrew Schofield (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-19363. -- Resolution: Fixed > Enhance share group assignor for heterogeneous subscription type >

[jira] [Resolved] (KAFKA-19362) Enhance share group assignor for homogeneous subscription type

2025-07-04 Thread Andrew Schofield (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-19362. -- Resolution: Fixed > Enhance share group assignor for homogeneous subscription type > -

Re: [PR] KAFKA-19363: Finalize heterogeneous simple share assignor [kafka]

2025-07-04 Thread via GitHub
AndrewJSchofield merged PR #20074: URL: https://github.com/apache/kafka/pull/20074 -- 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: jira-unsubscr...@kafk

[PR] KAFKA-19457: Make share group init retry interval configurable. [kafka]

2025-07-04 Thread via GitHub
smjn opened a new pull request, #20104: URL: https://github.com/apache/kafka/pull/20104 * While creating share group init requests in `GroupMetadataManager.shareGroupHeartbeat`, we check for topics in `initializing` state and if they are a certain amount of time old, we issue retry reque

Re: [PR] KAFKA-19048: Minimal movement replica balancing algorithm for reassignment [kafka]

2025-07-04 Thread via GitHub
Shihuan1014 commented on PR #19858: URL: https://github.com/apache/kafka/pull/19858#issuecomment-3035084703 Good work, in our business scenarios, topics are reassigned among dozens of brokers, optimizing the number of replicas movement is very helpful to us. -- This is an automated messag

[jira] [Resolved] (KAFKA-19456) State and leader epoch should only be used for validation and not be updated in share coordinator write state RPC.

2025-07-04 Thread Sushant Mahajan (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushant Mahajan resolved KAFKA-19456. - Fix Version/s: 4.2.0 Resolution: Fixed > State and leader epoch should only be us

[jira] [Resolved] (KAFKA-19455) Make unknown_topic_or_partition error retriable by the persister state manager.

2025-07-04 Thread Sushant Mahajan (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushant Mahajan resolved KAFKA-19455. - Fix Version/s: 4.2.0 Resolution: Fixed > Make unknown_topic_or_partition error re

[jira] [Resolved] (KAFKA-19454) Share group delete should be resilient to metadata image issues in group coordinator.

2025-07-04 Thread Sushant Mahajan (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushant Mahajan resolved KAFKA-19454. - Fix Version/s: 4.2.0 Resolution: Fixed > Share group delete should be resilient t

Re: [PR] KAFKA-19468: Ignore unsubscribed topics when computing share assignment [kafka]

2025-07-04 Thread via GitHub
AndrewJSchofield commented on code in PR #20101: URL: https://github.com/apache/kafka/pull/20101#discussion_r2184721496 ## group-coordinator/src/main/java/org/apache/kafka/coordinator/group/GroupMetadataManager.java: ## @@ -2692,7 +2690,27 @@ private boolean initializedAssignmen

Re: [PR] KAFKA-19468: Ignore unsubscribed topics when computing share assignment [kafka]

2025-07-04 Thread via GitHub
AndrewJSchofield commented on code in PR #20101: URL: https://github.com/apache/kafka/pull/20101#discussion_r2184719024 ## group-coordinator/src/main/java/org/apache/kafka/coordinator/group/GroupMetadataManager.java: ## @@ -2692,7 +2690,27 @@ private boolean initializedAssignmen

[jira] [Commented] (KAFKA-19469) Share group supports Dead Letter queue

2025-07-04 Thread Lan Ding (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17995698#comment-17995698 ] Lan Ding commented on KAFKA-19469: -- Great work! Looking forward to your KIP being publi

[jira] [Commented] (KAFKA-19469) Share group supports Dead Letter queue

2025-07-04 Thread Andrew Schofield (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17995695#comment-17995695 ] Andrew Schofield commented on KAFKA-19469: -- Yes, my thinking too. I have a KIP

Re: [PR] KAFKA-14915: allow read remote storage for multiple partitions in one fetchRequest [kafka]

2025-07-04 Thread via GitHub
satishd commented on PR #20045: URL: https://github.com/apache/kafka/pull/20045#issuecomment-3034779123 Thanks @showuon for the PR, I will review this PR by Monday. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the U

[jira] [Commented] (KAFKA-19444) SASL GSSAPI not working with librdkafka and AK 4.x

2025-07-04 Thread Emanuele Sabellico (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-19444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17993832#comment-17993832 ] Emanuele Sabellico commented on KAFKA-19444: librdkafka v2.11.0 with the fix