[jira] [Created] (KAFKA-19114) Backport KAFKA-18991 to 4.0, 3.9 and 3.8

Chia-Ping Tsai created KAFKA-19114: -- Summary: Backport KAFKA-18991 to 4.0, 3.9 and 3.8 Key: KAFKA-19114 URL: https://issues.apache.org/jira/browse/KAFKA-19114 Project: Kafka Issue Type: Sub-

[jira] [Resolved] (KAFKA-19093) Change the "Handler on Broker" to "Handler on Controller" for controller server

[ https://issues.apache.org/jira/browse/KAFKA-19093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-19093. Fix Version/s: 4.1.0 Resolution: Fixed > Change the "Handler on Broker" to "Handler

[jira] [Created] (KAFKA-19113) Migrate DelegationTokenManager to server module

PoAn Yang created KAFKA-19113: - Summary: Migrate DelegationTokenManager to server module Key: KAFKA-19113 URL: https://issues.apache.org/jira/browse/KAFKA-19113 Project: Kafka Issue Type: Sub-tas

Re: [DISCUSS] KIP-1152: Add transactional ID prefix filter to ListTransactions API

Hi Calvin, Thanks for the KIP! This is not an area of understanding (yet!) but had a few questions: KT01: I agree with David's DJ03. Would transactionalIdPattern or transactionalIdFilter still convey the idea? KT02: Can we change the command line option -transactionalIdPatternFilter to someth

[jira] [Created] (KAFKA-19112) cleanup.policy shouldn't be empty

Jun Rao created KAFKA-19112: --- Summary: cleanup.policy shouldn't be empty Key: KAFKA-19112 URL: https://issues.apache.org/jira/browse/KAFKA-19112 Project: Kafka Issue Type: Bug Components:

[jira] [Resolved] (KAFKA-18991) AbstractFetcherThread should verify the current leader epoch in the fetch request matches the leader epoch in the fetch state

[ https://issues.apache.org/jira/browse/KAFKA-18991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18991. - Resolution: Fixed > AbstractFetcherThread should verify the current leader epoch in the fetch > request

Re: KRaft controller disaster recovery

Hi Luke and Colin, On Mon, Apr 7, 2025 at 10:29 PM Luke Chen wrote: > That's why we were discussing if there's any way to "force" recover the > scenario, even if it's possible to have data loss. Yes. There is a way. They need to configure a controller cluster that matches the voter set in the cl

Re: KIP-1155: Metadata Version Downgrades [DISCUSS]

On Tue, Apr 8, 2025, at 09:55, Justine Olshan wrote: > Hey PoAn, > > Just wanted to make a clarification. TV2 doesn't need to be downgraded if > the MV is lower than the bootstrap MV for the TV. > The bootstrap MV is only used when the cluster is created to get the > default feature versions. As lo

Re: KRaft controller disaster recovery

On Mon, Apr 7, 2025, at 19:29, Luke Chen wrote: > Hi Jose and Colin, > > Thanks for your explanation! > > Yes, we all agree that 3 node quorum can only tolerate 1 node down. > We just want to discuss, "what if" 2 out of 3 nodes are down at the same > time, what can we do? > Currently, the result is

Re: KIP-1155: Metadata Version Downgrades [DISCUSS]

On Tue, Apr 8, 2025, at 01:58, PoAn Yang wrote: > Hi Colin, > > Thanks for the KIP. It’s good to give users more flexibility to > downgrade metadata.version. > > PY1: Each feature has bootstrapMetadataVersion. For example, TV_2 is > IBP_4_0_IV2. > Assume that a cluster uses TV_2 and metadata.vers

[jira] [Resolved] (KAFKA-19099) Remove GroupSyncKey, GroupJoinKey, and MemberKey

[ https://issues.apache.org/jira/browse/KAFKA-19099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-19099. Fix Version/s: 4.1.0 Resolution: Fixed > Remove GroupSyncKey, GroupJoinKey, and Mem

Re: KIP-1155: Metadata Version Downgrades [DISCUSS]

Hey PoAn, Just wanted to make a clarification. TV2 doesn't need to be downgraded if the MV is lower than the bootstrap MV for the TV. The bootstrap MV is only used when the cluster is created to get the default feature versions. As long as the TV version is a production version for the Kafka relea

[jira] [Created] (KAFKA-19111) Remove ModernGroup#computeSubscriptionMetadata unused parameter

黃竣陽 created KAFKA-19111: --- Summary: Remove ModernGroup#computeSubscriptionMetadata unused parameter Key: KAFKA-19111 URL: https://issues.apache.org/jira/browse/KAFKA-19111 Project: Kafka Issue Type: Im

Re: [DISCUSS] KIP-1158: Improve Connect SourceTask commit()

Consistent behavior sounds good to me! We should probably add a note on that to the Javadocs but I don't consider this a blocker. Thanks again, no further feedback from me. On Tue, Apr 8, 2025, 12:12 Sudesh Wasnik wrote: > Hello Chris ! Thanks for the quick review ! > > Good point, task.commit(

[jira] [Resolved] (KAFKA-19111) Remove ModernGroup#computeSubscriptionMetadata unused parameter

[ https://issues.apache.org/jira/browse/KAFKA-19111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 黃竣陽 resolved KAFKA-19111. - Resolution: Won't Fix > Remove ModernGroup#computeSubscriptionMetadata unused parameter > --

[jira] [Created] (KAFKA-19110) Add missing unit test for Streams-consumer integration

Bruno Cadonna created KAFKA-19110: - Summary: Add missing unit test for Streams-consumer integration Key: KAFKA-19110 URL: https://issues.apache.org/jira/browse/KAFKA-19110 Project: Kafka Iss

Re: [DISCUSS] KIP-1158: Improve Connect SourceTask commit()

Hi Sudesh, Thanks for the KIP. The existing commit method is... not great. I think the word "futile" you chose in the KIP is putting it lightly. The new interface looks clean, implementation seems extremely straightforward, and everything's backwards compatible. The only comment I'll leave is th

[jira] [Resolved] (KAFKA-18987) Include information about --standalone command in Static versus Dynamic KRaft Quorums documentation and errors

[ https://issues.apache.org/jira/browse/KAFKA-18987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 黃竣陽 resolved KAFKA-18987. - Resolution: Fixed This issue fixed by https://github.com/apache/kafka/pull/19210/files > Include information ab

[DISCUSS] KIP-1158: Improve Connect SourceTask commit()

Hi all, I would like to discuss KIP-1158. This KIP introduces a new "commit()" method in KafkaConnect SourceTask interface, primarily for use-cases where SourceConnectors need to track "source-offset" commits. Thanks in advance for reviewing ! KIP : https://cwiki.apache.org/confluence/pages/viewp

Coordinating Cross-Cluster Kafka Transactions with Exactly-Once Semantics

Hi Apache Kafka Community, I'm working on a problem involving cross-cluster data flow with exactly-once guarantees and would love to get your thoughts or experiences on this. The Setup: - I have a set of *consumers reading from a source topic* located on Kafka cluster *K1*. - The

[jira] [Resolved] (KAFKA-18892) Add support for ClientQuotaCallback

[ https://issues.apache.org/jira/browse/KAFKA-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-18892. Fix Version/s: 4.1.0 Resolution: Fixed > Add support for ClientQuotaCallback >

[jira] [Created] (KAFKA-19109) Don't print null in kafka-metadata-quorum describe status

José Armando García Sancio created KAFKA-19109: -- Summary: Don't print null in kafka-metadata-quorum describe status Key: KAFKA-19109 URL: https://issues.apache.org/jira/browse/KAFKA-19109

[jira] [Created] (KAFKA-19108) Consider improving the UI when describing static voters

José Armando García Sancio created KAFKA-19108: -- Summary: Consider improving the UI when describing static voters Key: KAFKA-19108 URL: https://issues.apache.org/jira/browse/KAFKA-19108 Pr

Re: [DISCUSS] KIP-1144: Exposing a new public REST API for MirrorMaker2

Hi Devs, I still want to sell this idea :) I think it would be really beneficial for the MM2 to have a proper REST API, to monitor the state of the replication flows. Please share your opinion on this. Thank you! On Tue, Mar 25, 2025 at 1:46 PM Kondrát Bertalan wrote: > Hi Team, > > I apprecia

Re: [DISCUSS] KIP-1157: Enforce KafkaPrincipalSerde Implementation for KafkaPrincipalBuilder

hi Johnny thanks for this KIP. Some questions are listed below. chia_0: could you please update the discussion link? chia_1: There are some discussion before. For example, we can introduce new interface consisting of KafkaPrincipalSerde and KafkaPrincipalBuilder to offer better naming. Could y

[jira] [Resolved] (KAFKA-19100) Use ProcessRole.toString instead of String in AclApis

[ https://issues.apache.org/jira/browse/KAFKA-19100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 黃竣陽 resolved KAFKA-19100. - Resolution: Fixed > Use ProcessRole.toString instead of String in AclApis >

Re: [DISCUSS] KIP-1157: Enforce KafkaPrincipalSerde Implementation for KafkaPrincipalBuilder

Hi Johnny, Thanks for this KIP. ken_0: Doesn't this change break backward compatibility? If a user has only implemented the `KafkaPrincipalBuilder` interface, upgrading to this version would result in a compilation error. Changes that break compatibility like this typically need to be reserve

[jira] [Created] (KAFKA-19106) Improve Connect SourceTask commit()

Sudesh Wasnik created KAFKA-19106: - Summary: Improve Connect SourceTask commit() Key: KAFKA-19106 URL: https://issues.apache.org/jira/browse/KAFKA-19106 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-19107) MirrorMaker2 repeatedly tries to sync group offsets for partitions that no longer exist

Alex Rovner created KAFKA-19107: --- Summary: MirrorMaker2 repeatedly tries to sync group offsets for partitions that no longer exist Key: KAFKA-19107 URL: https://issues.apache.org/jira/browse/KAFKA-19107

Re: KIP-1155: Metadata Version Downgrades [DISCUSS]

Hi Colin, Thanks for the KIP. It’s good to give users more flexibility to downgrade metadata.version. PY1: Each feature has bootstrapMetadataVersion. For example, TV_2 is IBP_4_0_IV2. Assume that a cluster uses TV_2 and metadata.version 4.0-IV2. If a user downgrades metadata.version to 3.9-IV0

[DISCUSS] KIP-1157: Enforce KafkaPrincipalSerde Implementation for KafkaPrincipalBuilder

Hi all, I would like to discuss KIP-1157. This KIP enforces the implementation of KafkaPrincipalSerde alongside KafkaPrincipalBuilder, which is currently only noted in the interface comments. Please take a look and share you thought. https://cwiki.apache.org/confluence/x/1gq9F Thanks, Wang

[VOTE] KIP-1142: Allow to list non-existent group which has dynamic config

Hi all, I would like to start a vote on KIP-1142. Thank you. KIP: https://cwiki.apache.org/confluence/x/AAqWF Discussion thread: https://lists.apache.org/thread/c3q584qtrodys2mkzdg0qxrktzbcjzmp Regards, PoAn

Re: Unexpected UNCLEAN leader election behaviour in KRaft vs. Zookeeper

Hello Colin, thanks for your reply. I use unclean.leader.election.enable to false on all controllers and brokers. BR, Julian From: Colin McCabe Date: Monday, 7. April 2025 at 23:54 To: dev@kafka.apache.org Subject: Re: Unexpected UNCLEAN leader election behaviour in KRaft vs. Zookeeper Did yo

[jira] [Created] (KAFKA-19105) Add Audit Logging for Authentication Events with Performance Consideration

lujie created KAFKA-19105: - Summary: Add Audit Logging for Authentication Events with Performance Consideration Key: KAFKA-19105 URL: https://issues.apache.org/jira/browse/KAFKA-19105 Project: Kafka