Re: [SPAM][DISCUSS] KIP-1164: Topic Based Batch Coordinator

Thanks Giuseppe for the explanation! It make sense to me. Best regards, Yuxia - 原始邮件 - 发件人: "Giuseppe Lillo" 收件人: "dev" 发送时间: 星期二, 2025年 4 月 29日 上午 12:14:14 主题: Re: [SPAM][DISCUSS] KIP-1164: Topic Based Batch Coordinator Hello Yuxia, thanks for your question and interest! When produci

Re: [DISCUSS] KIP-1162: Redesign ClientQuotaCallback#updateClusterMetadata

hi Colin the interface `ClientQuotaCallackHandler` is a typo - the idea of this PR is to add new `updateClusterMetadata` to replace/deprecate old `updateClusterMetadata`. Additionally, the production code will call new `updateClusterMetadata` instead of old `updateClusterMetadata`. That means use

Re: [VOTE] KIP-1141: Simplifying MetadataQuorumCommand by Leveraging Admin API for Controller Management

Hi Colin, I just wanted to make sure I’m on the right track, so I’m sharing my understanding of the current process for adding a controller to the voter set. Here's what I think it looks like: Step 1: Use kafka-storage.sh format to format the controller. Step 2: Start up the controller and ensure

Re: [VOTE] 3.9.1 RC1

Hi everyone, I want to bump this thread since the RC vote is about to be due. Thanks for your attention. Best, TengYao Edoardo Comar 於 2025年4月25日 週五 下午9:32寫道： > Luke, TengYao > https://github.com/apache/kafka/pull/19563 > > On Fri, 25 Apr 2025 at 12:18, Edoardo Comar wrote: > > > > Hi Luke,

Jenkins build is still unstable: Kafka » Kafka PowerPC Daily » test-powerpc #282

See

Re: [VOTE] KIP-1141: Simplifying MetadataQuorumCommand by Leveraging Admin API for Controller Management

So to expand a bit on what I wrote below: - If the goal is to make it possible to have adding the controller node happen in one place, and formatting the controller node happen in another, those two places still need to communicate. What they need to communicate is the new directory ID. This is

Re: [DISCUSS] KIP-1166: Improve high-watermark replication

Hi José, Thank you for this much-needed improvement to metadata propagation. Maybe I missed something, but even after reading the discussion below, I still don't understand the rationale for separating the "RPC version too old" and "high watermark not known" cases. Is the idea that separating t

Re: [VOTE] KIP-1146: Anchored punctuation

+1 (binding) On 4/28/25 2:24 PM, Sophie Blee-Goldman wrote: Looks great, +1 (binding) On Mon, Apr 28, 2025 at 4:47 AM Herman K. Jakobsen < hermankjakob...@gmail.com> wrote: Hi, I would like to start a vote on KIP-1146: Anchored punctuation - Apache Kafka - Apache Software Foundation < https:/

[jira] [Created] (KAFKA-19212) Fix ElectionWasClean method bug when partition reassignment completes

Calvin Liu created KAFKA-19212: -- Summary: Fix ElectionWasClean method bug when partition reassignment completes Key: KAFKA-19212 URL: https://issues.apache.org/jira/browse/KAFKA-19212 Project: Kafka

Re: [DISCUSS] KIP-1166: Improve high-watermark replication

Hi David, Thanks for the feedback. On Mon, Apr 28, 2025 at 2:51 PM David Arthur wrote: > DA1. It might be more clear if we call the field something like > "LastFetchedHighWaterMark" (similar to "LastFetchedEpoch"). "HighWaterMark" > is already very prevalent in ReplicaManager, so it might be nic

Re: [VOTE] KIP-1146: Anchored punctuation

Looks great, +1 (binding) On Mon, Apr 28, 2025 at 4:47 AM Herman K. Jakobsen < hermankjakob...@gmail.com> wrote: > Hi, > I would like to start a vote on KIP-1146: Anchored punctuation - Apache > Kafka - Apache Software Foundation > < > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1146%3A

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

Hi, Can you clarify the discussion about compatibility? I wasn't able to figure out whether the change is compatible or not based on reading through the KIP. If it is not compatible, what specific actions are needed from users? best, Colin On Tue, Mar 25, 2025, at 05:10, TengYao Chi wrote: > H

Re: [VOTE] KIP-1148: Remove log.cleaner.enable configuration

+1 (binding) thanks, Colin On Thu, Apr 10, 2025, at 05:22, Jhen-Yung Hsu wrote: > Thanks for the KIP! > > +1 (non-binding) > > On 2025/04/10 07:51:53 TengYao Chi wrote: >> Hello everyone, >> >> I would like to call a vote on KIP-1148 >> . >> >> Here

Re: [ANNOUNCE] New committer: Apoorv Mittal

Congrats, Apoorv! best, Colin On Sat, Apr 12, 2025, at 06:58, Mingdao wrote: > Congratulations, Apoorv! > > On Sat, Apr 12, 2025 at 9:39 PM Kirk True wrote: > >> Congratulations Apoorv. Justly deserved! >> >> On Sat, Apr 12, 2025, at 12:22 AM, Kamal Chandraprakash wrote: >> > Congratulations, Ap

Re: [ANNOUNCE] New committer: TengYao Chi

Congratulations! best, Colin On Sat, Apr 12, 2025, at 06:39, Kirk True wrote: > Congratulations TengYao! > > On Sat, Apr 12, 2025, at 12:21 AM, Kamal Chandraprakash wrote: >> Congrats, TengYao! Well deserved!! >> >> On Sat, Apr 12, 2025 at 7:19 AM Guozhang Wang >> wrote: >> >> > Congratulation

Re: [DISCUSS] KIP-1173: Connect Storage Topics Sharing Across Clusters

Hi Pritam, Thanks for the KIP! I'm a little unsure of the motivation here and would appreciate some more context from your experience. 1. The KIP states "Broker resource utilization is expected to decrease by approximately 20%, primarily due to reduced partition count and metadata overhead." Can

Re: [DISCUSS] KIP-1162: Redesign ClientQuotaCallback#updateClusterMetadata

Hi Kuan Po Tseng, Thank you for starting this discussion. This would be a very nice improvement. It seems that the current scheme requires everyone writing an implementation of ClientQuotaCallackHandler to implement the old updateClusterMetadata function that takes a Cluster. That seems less th

Re: [VOTE] KIP-1131: Improved controller-side monitoring of broker states

Thanks Kevin, +1 (binding) from me as well. Justine On Mon, Apr 28, 2025 at 10:20 AM Kevin Wu wrote: > Hey PoAn, > > I might be wrong, but I thought you were a committer? If so, are you > willing to change your vote to be binding if the changes look good, so the > KIP is accepted? > > Best reg

Re: [VOTE] KIP-1141: Simplifying MetadataQuorumCommand by Leveraging Admin API for Controller Management

Hi Kuan Po Tseng, It is not possible to add a new controller purely by ID. You need controller ID, directory ID, and controller endpoints. These cannot be obtained through describeMetadataQuorum since that only describes the existing quorum, not what you would like the new one to be. Also, obv

Re: [DISCUSS] KIP-1166: Improve high-watermark replication

Hey José, thanks for the KIP! If I understand correctly, the problem at hand is that the follower may need a new HWM, but if there is no new data waiting it can take up to MaxWaitMs. Having the follower report its HWM in the request seems like a good approach. DA1. It might be more clear if we ca

[DISCUSS] KIP-1174: Expose addReadOnlyStateStore in DSL (StreamsBuilder)

Hello Kafka Community, I would like to propose a KIP-1174 to expose the addReadOnlyStateStore functionality in the high-level DSL API (StreamsBuilder). This KIP aims

Re: [VOTE] KIP-1131: Improved controller-side monitoring of broker states

Hey PoAn, I might be wrong, but I thought you were a committer? If so, are you willing to change your vote to be binding if the changes look good, so the KIP is accepted? Best regards, Kevin On Tue, Mar 25, 2025 at 5:29 PM Kevin Wu wrote: > Hello all, > > I am manually bumping this thread. > A

Re: [SPAM][DISCUSS] KIP-1164: Topic Based Batch Coordinator

Hello Yuxia, thanks for your question and interest! When producing, the broker will call the relevant Batch Coordinator with a CommitBatches request. The Batch Coordinator will then write the metadata about these batches into the __diskless-metadata topic and update its internal state persisted on

Re: [VOTE] KIP-1152: Add transactional ID pattern filter to ListTransactions API

Hi, the KIP has received 4 binding votes from David, Chia-Ping, Jun and Justine! 1 non-binding vote from Kirk! So the KIP is accepted! Thanks everyone! On Thu, Apr 24, 2025 at 4:49 PM Justine Olshan wrote: > Yay, > +1 from me. > > Thanks Calvin! > > On Thu, Apr 24, 2025 at 10:12 AM Jun Rao wrot

[DISCUSS] KIP-1173: Connect Storage Topics Sharing Across Clusters

Hi Kafka Community, I'd like to start a discussion on KIP-1173: Connect Storage Topics Sharing Across Clusters . The primary motivation for writing this KIP and proposing this enhancemen

[jira] [Created] (KAFKA-19211) Connect Storage Topics Sharing Across Clusters

Pritam Kumar created KAFKA-19211: Summary: Connect Storage Topics Sharing Across Clusters Key: KAFKA-19211 URL: https://issues.apache.org/jira/browse/KAFKA-19211 Project: Kafka Issue Type: Im

[jira] [Created] (KAFKA-19210) investigate flakiness in GroupMetadataManagerTest.testShareGroupHeartbeatInitializeOnPartitionUpdate

Chirag Wadhwa created KAFKA-19210: - Summary: investigate flakiness in GroupMetadataManagerTest.testShareGroupHeartbeatInitializeOnPartitionUpdate Key: KAFKA-19210 URL: https://issues.apache.org/jira/browse/KAFKA-1

[VOTE] KIP-1146: Anchored punctuation

Hi, I would like to start a vote on KIP-1146: Anchored punctuation - Apache Kafka - Apache Software Foundation . - Herman

[jira] [Created] (KAFKA-19209) "index.interval.bytes" config doc should also mention time index

Luke Chen created KAFKA-19209: - Summary: "index.interval.bytes" config doc should also mention time index Key: KAFKA-19209 URL: https://issues.apache.org/jira/browse/KAFKA-19209 Project: Kafka I