[jira] [Resolved] (KAFKA-15621) Add histogram metrics to GroupCoordinatorRuntimeMetrics

[ https://issues.apache.org/jira/browse/KAFKA-15621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-15621. - Fix Version/s: 4.0.0 Resolution: Fixed > Add histogram metrics to GroupCoordinatorRuntime

[jira] [Resolved] (KAFKA-15756) Migrate existing integration tests to run old protocol in new coordinator

[ https://issues.apache.org/jira/browse/KAFKA-15756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-15756. - Resolution: Won't Do The new group coordinator is now used by default so all the tests use it by

[jira] [Resolved] (KAFKA-16830) Remove the scala version formatters support

[ https://issues.apache.org/jira/browse/KAFKA-16830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16830. Resolution: Fixed > Remove the scala version formatters support >

[jira] [Created] (KAFKA-17508) Adding some guard for fallback deletion logic

Luke Chen created KAFKA-17508: - Summary: Adding some guard for fallback deletion logic Key: KAFKA-17508 URL: https://issues.apache.org/jira/browse/KAFKA-17508 Project: Kafka Issue Type: Improveme

Re: [DISCUSS] KIP-1073 Return inactive observer nodes in DescribeQuorum response

Thank you Luke for taking a look again. If there are no further comments, I would like to start the vote for this KIP tomorrow. Regards, Gantigmaa On Thu, Sep 5, 2024 at 8:30 AM Luke Chen wrote: > Hi Tina, > > Thanks for updating the KIP. > This change makes sense to me. > > Thanks. > Luke > >

[jira] [Resolved] (KAFKA-17478) Wrong configuration of metric.reporters lead to NPE in KafkaProducer constructor

[ https://issues.apache.org/jira/browse/KAFKA-17478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17478. Fix Version/s: 4.0.0 Resolution: Fixed > Wrong configuration of metric.reporters le

[jira] [Resolved] (KAFKA-17306) Soften the validation when replaying tombstones

[ https://issues.apache.org/jira/browse/KAFKA-17306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-17306. - Fix Version/s: 4.0.0 Resolution: Fixed > Soften the validation when replaying tombstones

[jira] [Resolved] (KAFKA-17224) Make ForeachProcessor internal

[ https://issues.apache.org/jira/browse/KAFKA-17224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17224. Fix Version/s: 4.0.0 Resolution: Fixed > Make ForeachProcessor internal > -

Re: [VOTE] KIP-1080: Fix the typo: `maxlifeTimeMs` in CreateDelegationTokenOptions

Hello, Thanks for updating the KIP. Looks good to me now. +1 (binding) Lianet On Thu, Sep 5, 2024, 8:29 p.m. 黃竣陽 wrote: > It make sense to me, I will change to > `CreateDelegationTokenRequestData.setMaxLifetimeMs` > > > Chia-Ping Tsai 於 2024年9月5日 晚上11:22 寫道： > > > >> it aligns better with t

Re: [DISCUSS] KIP-1073 Return inactive observer nodes in DescribeQuorum response

Gantigmaa, thanks for the changes, they look good to me in general, I have some UX questions. The KIP mentions the following: > Also if there is no rack information for any of the nodes, the RACK column > will be omitted from the output. What will the tool output for nodes that don't have a rack

[jira] [Created] (KAFKA-17515) Fix flaky RestoreIntegrationTest.shouldInvokeUserDefinedGlobalStateRestoreListener

Chia-Ping Tsai created KAFKA-17515: -- Summary: Fix flaky RestoreIntegrationTest.shouldInvokeUserDefinedGlobalStateRestoreListener Key: KAFKA-17515 URL: https://issues.apache.org/jira/browse/KAFKA-17515

Re: [DISCUSS] Single broker failures causing offline partitions

Hey Martin. I recommend you take a look at KIP-966. I think can help the use case you are describing. The KIP talks about failure scenarios, but I believe it will also help when the leader has issues and kicks its followers out of ISR. The goal is to better handle the "last replica standing" issue

Re: [DISCUSS] Single broker failures causing offline partitions

Hi Justine, Indeed we are very much interested in the improvements that will come from KIP-966! However I think there is still a gap regarding the failure detection of the leader. Please correct me if this is wrong but my understanding is that with KIP-966 we'll stop advancing the HWM minISR isn'

Kafka MirrorMaker2 not replicating consumer group offset

When I create a new topic in source cluster with few messages, the new topic will be replicated successfully to target cluster in few seconds. Then I create a consumer group in source, consume 1 message in source, this consumer group will also be replicated successfully to target cluster. Current o

[jira] [Resolved] (KAFKA-17492) skip features with minVersion of 0 instead of replacing 0 with 1 when BrokerRegistrationRequest < 4

[ https://issues.apache.org/jira/browse/KAFKA-17492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17492. Fix Version/s: 3.9.0 Resolution: Fixed trunk: https://github.com/apache/kafka/comm

[jira] [Resolved] (KAFKA-17458) Add 3.8 to transactions_upgrade_test.py, transactions_mixed_versions_test.py, and kraft_upgrade_test.py

[ https://issues.apache.org/jira/browse/KAFKA-17458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17458. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/0af75c0e41184e362efca2531

[jira] [Created] (KAFKA-17516) Client metrics configuration resources default configs not shown by Kafka-config.sh

Andrew Schofield created KAFKA-17516: Summary: Client metrics configuration resources default configs not shown by Kafka-config.sh Key: KAFKA-17516 URL: https://issues.apache.org/jira/browse/KAFKA-17516

[VOTE] KIP-1064 - Upgrade slf4j to 2.x

Hi all, I would like to call a vote on KIP-1064 - Upgrade slf4j to 2.x Target version : 4.0.0 KIP - https://cwiki.apache.org/confluence/display/KAFKA/KIP-1064%3A+Upgrade+slf4j+to+2.x Discussion thread - https://lists.apache.org/thread/z05rlzbjv89rpvzjmzsr8v4w17qn21r1 Jira with some discussion

Re: [DISCUSS] Single broker failures causing offline partitions

Hi Martin. Yes, the KIP-966 does not resolve your concern for the degraded leader. To fill the gap, 1. As you have mentioned, we need a leader degradation detection mechanism. So that the controller can promote another replica to the leader. 2. The controller needs to know which replica is a valid

[jira] [Resolved] (KAFKA-15793) Flaky test ZkMigrationIntegrationTest.testMigrateTopicDeletions

[ https://issues.apache.org/jira/browse/KAFKA-15793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-15793. -- Resolution: Fixed > Flaky test ZkMigrationIntegrationTest.testMigrateTopicDeletions >

Re: [DISCUSS] KIP-1071: Streams Rebalance Protocol

Just following up to say thank you Lucas for the detailed explanations, and especially the thorough response to my more "existential" questions about building off 848 vs introducing a separate Streams group protocol. This really helped me understand the motivations behind this decision. No notes!

Re: [ANNOUNCE] New committer: Jeff Kim

congrats! On Tue, Sep 10, 2024 at 5:02 PM Kirk True wrote: > Congratulations Jeff! > > > On Sep 9, 2024, at 6:25 PM, Matthias J. Sax wrote: > > > > Congrats! > > > > On 9/9/24 12:34 PM, José Armando García Sancio wrote: > >> Congratulations Jeff! > >> On Mon, Sep 9, 2024 at 11:45 AM Justine Ols

[jira] [Created] (KAFKA-17519) Review intended behavior of Consumer.close() and its timeout on interrupt

Kirk True created KAFKA-17519: - Summary: Review intended behavior of Consumer.close() and its timeout on interrupt Key: KAFKA-17519 URL: https://issues.apache.org/jira/browse/KAFKA-17519 Project: Kafka

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

I was working on the PR for this KIP and realized that there is only one implementation of the handler, namely `DefaultProductionExceptionHandler` which does return FAIL right now. Thus, we only need to update this handler. I updated the KIP accordingly. -Matthias On 8/22/24 11:27, Matthias

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

See

Re: [VOTE] KIP-1064 - Upgrade slf4j to 2.x

+1 (binding) BTW, could you please add "compatibility issue" to the motivation? the version of slf4j provider must be equal to slf4j API [0]. Including both in kafka distribution can avoid compatibility issue; [0] https://www.slf4j.org/manual.html#compatibility Muralidhar Basani 於 2024年9月11日 週

[jira] [Resolved] (KAFKA-17435) remove use.incremental.alter.configs

[ https://issues.apache.org/jira/browse/KAFKA-17435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17435. Fix Version/s: 4.0.0 Resolution: Fixed > remove use.incremental.alter.configs > ---