Re: [DISCUSS] KIP-595: A Raft Protocol for the Metadata Quorum

Big +1 for your initiative and I have a question, we implement the Raft protocol just to be used in the management of metadata in Zookeeper or we will also use it to replace the current logical of managing log-replica since the algorithm we used to manage log-replica is analogous to Raft. On Fri,

Re: [DISCUSS] KIP-858: Handle JBOD broker disk failure in KRaft

Hi Igor, I think this KIP can solve the current problems, I have some problems relating to the migration section. Since we have bumped broker RPC version and metadata record version, there will be some problems between brokers/controllers of different versions. In ZK mode we use IBP as a flag

Re: [DISCUSS] KIP-868 Metadata Transactions (new thread)

Hello David, Thanks for the KIP, certainly it makes sense, I left some minor questions. 1. In “Record Visibility” section you declare visibility in the controller, in “Broker Support” you mention visibility in the broker, we can put them together, and I think we can also describe visibility in t

Re: [DISCUSS] KIP-868 Metadata Transactions (new thread)

data records end up in org.apache.kafka.common.metadata, so > maybe we can avoid Metadata in the name since it's kind of implicit. > I'd be okay with [Begin|End|Abort]TransactionRecord. > > -David > > On Mon, Sep 19, 2022 at 10:58 PM deng ziming > wrote: > >

Re: [jira] [Created] (KAFKA-14257) Unexpected error INCONSISTENT_CLUSTER_ID in VOTE response

Hello jianbin, This error happens when the clusterIds are inconsistent among all kraft voters, have you checked the cluster.id in your meta.properties(meta.properties is generated using `kafka-storage.sh`) ? -- Ziming On Fri, Sep 23, 2022 at 9:41 AM jianbin.chen (Jira) wrote: > jianbin.chen cre

Re: [VOTE] KIP-868 Metadata Transactions

Thanks for this KIP, +1(non-binding) from me. -- Best, Ziming > On Sep 28, 2022, at 10:05 PM, David Jacot wrote: > > +1 (binding). Thanks for the KIP. I really like the approach! > > Best, > David > > On Wed, Sep 28, 2022 at 4:20 AM Luke Chen wrote: >> >> Hi David, >> >> +1 (binding) from

Re: [ANNOUNCE] New committer: Deng Ziming

; > > > > Ismael > > > > > > > > On Mon, Oct 10, 2022 at 9:30 AM Jason Gustafson > > > > > > > > > > > wrote: > > > > > > > > > Hi All > > > > > > > > > > The PMC for Apache K

Re: question

Hello jincheng, Kafka provides Java Producer/Consumer/Admin public api, so you can access Kafka if you are using Java to develop an Android App even though it's not common. for example, you can develop an Android App to get the Kafka metadata, send bury-point event log to Kafka, however, a better s

Re: [VOTE] KIP-876: Time based cluster metadata snapshots

Thanks for this KIP, +1 for this(binding). -- Best, Ziming > On Oct 14, 2022, at 8:11 AM, José Armando García Sancio > wrote: > > Hello all, > > I would like to start voting for "KIP-876: Time based cluster metadata > snapshots." > > KIP: https://cwiki.apache.org/confluence/x/MY3GDQ > Discu

Re: [ANNOUNCE] New Kafka PMC Member: Bruno Cadonna

Congrats! -- Ziming > On Nov 2, 2022, at 3:36 AM, Guozhang Wang wrote: > > Hi everyone, > > I'd like to introduce our new Kafka PMC member, Bruno. > > Bruno has been a committer since April. 2021 and has been very active in > the community. He's a key contributor to Kafka Streams, and also he

Re: [VOTE] KIP-893: The Kafka protocol should support nullable structs

+1 (binding) -- Thanks, Ziming > On Dec 6, 2022, at 10:48, John Roesler wrote: > > +1 (binding) > > Thanks, > -John > > On Mon, Dec 5, 2022, at 16:57, Kirk True wrote: >> +1 (non-binding) >> >> On Mon, Dec 5, 2022, at 10:05 AM, Colin McCabe wrote: >>> +1 (binding) >>> >>> best, >>> Colin >

Re: [VOTE] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

hi, I reviewed the current code, the ProduceMetadata maintains an expiry threshold for every topic, every time when we write to a topic we will set the expiry time to -1 to indicate it should be updated, this does work to reduce the size of the topic working set, but the producer will continue fetc

Re: [VOTE] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

n bring the blocking problem? On Wed, Nov 20, 2019 at 12:40 AM Brian Byrne wrote: > Hi Deng, > > Thanks for the feedback. > > On Mon, Nov 18, 2019 at 6:56 PM deng ziming > wrote: > > > hi, I reviewed the current code, the ProduceMetadata maintains an expiry > >

Re: [DISCUSS] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

I think it's ok, and you can add another issue about `asynchronous metadata` if `topic expiry` is not enough. On Thu, Nov 21, 2019 at 6:20 AM Brian Byrne wrote: > Hello all, > > I've refactored the KIP to remove implementing asynchronous metadata > fetching in the producer during send(). It's n

Re: [DISCUSS] KIP-547: Extend ConsumerInterceptor to allow modification of Consumer Commits

Hi, Eric what's the use of this method? I reviewed the code and couldn't find much of the metadata's usage, and I find its usage trivial. On Tue, Nov 19, 2019 at 3:19 AM Eric Azama wrote: > Hi all, > > I'd like to open discussion on KIP-547: Extend ConsumerInterceptor to allow > modification of

Re: [jira] [Created] (KAFKA-9217) Partial partition's log-end-offset is zero

hello lisen, > > The amount of data my consumers consume is 400222 > do you consume all partitions from offset 0? if yes, this may probably be a bug. On Thu, Nov 21, 2019 at 3:22 PM lisen (Jira) wrote: > lisen created KAFKA-9217: > > > Summary: Partial

[issue assign]

hello, I read the Contributing Code Changes page which says I can assign a ticket to myself but it turns out that I can't assign? how could I assign it to myself? thank you! [image: image.png]

Re: [issue assign]

my jira username is : dengziming thank you On Fri, Nov 29, 2019 at 11:31 AM Gurudatt Kulkarni wrote: > Share your jira username here. > > On Friday, November 29, 2019, deng ziming > wrote: > > hello, I read the Contributing Code Changes page which says I can assign > a ti

[jenkins problem]

I always receive these kinds of messages about jenkins failed, and most prs of Kafka build failed even just a trivial change，can someone inspects it. [image: image.png] [image: image.png]

Re: Group Metadata Manager on Broker 3]: Error in loading offsets from [__consumer_offsets,34] (kafka.coordinator.GroupMetadataManager) kafka.common.KafkaException: Unknown group metadata version 1

I once encountered the same problem when I installed 2 versions of Kafka with the same config, and startup version A Kafka firstly and shutdown it, and misoperated to start version B Kafka secondly and write some data to it and shutdown it, and then startup version A Kafka. I think it's OK to igno

Re: Permission to create KIP

hi,Matthias also add me,thank you, my wiki id is dengziming On Tue, Dec 31, 2019 at 3:12 AM Matthias J. Sax wrote: > Done. > > On 12/30/19 8:00 AM, Sagar wrote: > > Hi, > > > > Its sagarmeansocean > > > > On Sat, Dec 28, 2019 at 12:29 AM Matthias J. Sax > > wrote: > > > >> What is your wiki acc

[DISCUSS] KIP-813: Replace KafkaConsumer with AdminClient in GetOffsetShell

Hi everyone, I would like to start a discussion for KIP-813 https://cwiki.apache.org/confluence/display/KAFKA/KIP-813%3A+Replace+KafkaConsumer+with+AdminClient+in+GetOffsetShell

Re: [DISCUSS] KIP-813: Replace KafkaConsumer with AdminClient in GetOffsetShell

Thank you Luke, I fleshed my KIP according to your suggestions, mostly in the Public Interfaces section. Please take a review again. Ziming Deng > On Jan 15, 2022, at 11:09 AM, Luke Chen wrote: > > Hi Ziming, > > Thanks for the KIP! > It's good to support fetch max timestamp in GetOffsetSh

Re: [DISCUSS] KIP-813: Replace KafkaConsumer with AdminClient in GetOffsetShell

ell me what you think! > > Cheers, > D. > > From: deng ziming > Date: Friday, 14 January 2022 at 14:42 > To: dev@kafka.apache.org > Subject: [DISCUSS] KIP-813: Replace KafkaConsumer with AdminClient in > GetOffsetShell > Hi everyone, > > I would like to start a

[DISCUSS] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

Hi everyone, I would like to restart a discussion for KIP-815 since the old KIP number conflict with another KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-815%3A+Replace+KafkaConsumer+with+AdminClient+in+GetOffsetShell

Re: [DISCUSS] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

Thank you Luke, I already changed the file name. > On Jan 20, 2022, at 10:08 AM, Luke Chen wrote: > > Hi Ziming, > > Thanks for the update! It looks good now. > > Only 1 minor comment: > The file name in example can change to `kafka_admin_client.properties`, > which should be much clear. > >

Re: [DISCUSS] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

Hi everyone, I will start a voting progress soon if no body has more concerns. > On Jan 25, 2022, at 1:04 PM, deng ziming wrote: > > Thank you Luke, I already changed the file name. > >> On Jan 20, 2022, at 10:08 AM, Luke Chen wrote: >> >> Hi Ziming, >>

[VOTE] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

Hey all, I'm starting the voting on KIP-734. This supports a new OffsetSpec in GetOffsetShell so that we can easily determine the offset and timestamp of the message with the largest timestamp on a partition. This seems a simple change but replaced KafkaConsumer with AdminClient in GetOffset

Re: [VOTE] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

Sorry all, I mean KIP-851 not KIP-734. In KIP-734 we add a new OffsetSpec to AdminClient, in this KIP I just extend this OffsetSpec to GetOffsetShell. > On Jan 30, 2022, at 6:29 PM, deng ziming wrote: > > Hey all, I'm starting the voting on KIP-734. > > This supports

[VOTE] KIP-815: Support max-timestamp in GetOffsetShell

. That would be another way to > address the issue. However, I agree > with you that using the admin client is better in the admin tools. > > Best, > David > > On Sun, Jan 30, 2022 at 2:09 PM deng ziming wrote: >> >> Sorry all, I mean KIP-851 not KIP-734. >&g

Re: [VOTE] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

ransition won't be >> noticed. I might be speculating here. >> >> 4. For completeness, I think that we should mention extending the >> consumer to support max-timestamp >> as well in the rejected alternatives. That would be another way to >> address the issue.

Re: [ANNOUNCE] New committer: Luke Chen

Congratulations, Luke! Thanks, Ziming Deng > On Feb 10, 2022, at 9:39 AM, John Roesler wrote: > > Congratulations, Luke! > -John > > On Wed, Feb 9, 2022, at 19:33, Mayuresh Gharat wrote: >> Congratulations Luke! >> >> Thanks, >> >> Mayuresh >> >> On Wed, Feb 9, 2022, 5:24 PM Ismael Juma w

Re: [VOTE] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

inClient will > behave slightly > differently. However, as it seems to be a bug, we will fix the Consumer and we > can add a link to the Jira. > > It is important to get this section as clear as possible because this > is where questions > will be. > > Cheers, > David

[VOTE] KIP-815: Support max-timestamp in GetOffsetShell

Hey all, I'm starting the voting on KIP-815. This supports a new OffsetSpec in GetOffsetShell so that we can easily determine the offset and timestamp of the message with the largest timestamp on a partition. This seems a simple change but replaced KafkaConsumer with AdminClient in GetOffsetShe

Re: [VOTE] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

est, > David > > On Fri, Feb 11, 2022 at 2:57 PM deng ziming wrote: >> >> David, Thank you for pointing out this. >> >> After some time, I sorted out the main configurations, the main difference >> are default.api.timeout.ms <http://default.api.timeou

Re: [VOTE] KIP-815: Support max-timestamp in GetOffsetShell

erence, here is the KIP: >>> >>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-815%3A++Support+max-timestamp+in+GetOffsetShell >>> >>> Thanks for the KIP! +1 (binding) >>> >>> Best, >>> David >>> >>> Le mar. 22 fév

Re: [VOTE] KIP-815: Support max-timestamp in GetOffsetShell

s the KIP: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-815%3A++Support+max-timestamp+in+GetOffsetShell > > Thanks for the KIP! +1 (binding) > > Best, > David > > Le mar. 22 févr. 2022 à 04:03, deng ziming a > écrit : > >> Hey all, I'm starting

Re: [DISCUSS] Apache Kafka 3.2.0 release

Hey Bruno, Can we add KIP-815 to the plan? https://cwiki.apache.org/confluence/display/KAFKA/KIP-815%3A++Support+max-timestamp+in+GetOffsetShell The vote has passed just 2 days ago. — Thanks,

Re: [VOTE] KIP-792: Add "generation" field into consumer protocol

Thank you Luke for this work, I’m +1(non-binding) -- Best, Ziming Deng > On Dec 1, 2021, at 8:36 AM, Luke Chen wrote: > > Hi all, > > I'd like to start the vote for KIP-792: Add "generation" field into > consumer protocol. > > The goal of this KIP is to allow the assignor/consumer coordinator

Re: Request for pull request review

Hello Igor, Thank you for driving this, currently we have more discussion about this, the main concern is that we don't want to add an RPC which will be O(num_partitions_in_dir), please see https://issues.apache.org/jira/browse/KAFKA-9837 for m

Re: [DISCUSS] KIP-836: Addition of Information in DescribeQuorumResponse about Voter Lag

Hello Niket, currently DescribeQuorumResponse is not a public API, we don’t have a Admin api or shell script to get DescribeQuorumResponse, so it’s unnecessary to submit a KIP to change it, you can just submit a PR to accomplish this. -- Thanks Ziming > On May 10, 2022, at 1:33 AM, Niket Goel

Re: [VOTE] KIP-831: Add metric for log recovery progress

Hello Luke, thanks for this KIP, +1 (non-binding) -- Best, Ziming > On May 16, 2022, at 3:59 PM, Divij Vaidya wrote: > > +1 (non-binding) > > > Divij Vaidya > > > > On Mon, May 16, 2022 at 10:12 AM Luke Chen wrote: > >> Hi all, >> >> I'd like to start a vote on KIP to expose metrics fo

Re: CI on Kafka seems to be failing even on trunk branch

You can help to solve this bug first if you are free, https://issues.apache.org/jira/browse/KAFKA-13907 , since this bug can be reproduced locally, it won't be hard to investigated. > On May 17, 2022, at 12:34 AM, Lim Qingwei wrote: > > Hi, I

Re: [DISCUSS] KIP-836: Addition of Information in DescribeQuorumResponse about Voter Lag

Hello Niket, 1. I find the DescribeQuorumResult still contains an DescribeQuorumResponseData, which is not allowed as Jose commented, have you forgot to change it? 2. You only add an Handle in AdminClient, can you also add an `kafka-metadata-quorum.sh` tool to help this? > On May 17, 2022,

Re: [VOTE] KIP-836: Addition of Information in DescribeQuorumResponse about Voter Lag

+1(non-binding) Thanks for this KIP. -- Best, Ziming > On May 17, 2022, at 1:14 AM, Niket Goel wrote: > > Hi all, > > I would like to start a vote for KIP-836: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-836%3A+Addition+of+Information+in+DescribeQuorumResponse+about+Voter+Lag > >

Re: [DISCUSS] KIP-842: Add richer group offset reset mechanisms

Thank you for this KIP, the motivation makes sense to me, left some questions: 1. If strategy=safe_latest and there is not committed offset, we have 2 choices based on whether the group is started newly, can you elaborate on how can we decide the group is started newly? It would be clear. 2. If

Re: [DISCUSS] KIP-840: Config file option for MessageReader/MessageFormatter in ConsoleProducer/ConsoleConsumer

Thanks for the KIP, this is a good improvement. I only have one minor suggestion. Currently many command line tools supports config file argument, but their name style is not unified, for example, most newly added tools are using --command-config, but ConsoleConsumer use —consumer.config。 I thi

Re: [DISCUSS] KIP-842: Add richer group offset reset mechanisms

kip-842. > > > > > 4. The meaning of nearest.offset.reset has been clearly expressed in point 2, > this configuration is disabled default, that is to say, when out-of-range, > reset strategy is performed according to the main strategy > (auto.offset.reset). > >

Re: [VOTE] KIP-840: Config file option for MessageReader/MessageFormatter in ConsoleProducer/ConsoleConsumer

Thank you for this KIP, +1 (non-binding) -- Best, Ziming > On Jun 7, 2022, at 8:53 PM, Alexandre Garnier wrote: > > Hi! > > A little reminder to vote for this KIP. > > Thanks. > > > Le mer. 1 juin 2022 à 10:58, Alexandre Garnier a écrit : >> >> Hi everyone! >> >> I propose to start vot

Re: [VOTE] KIP-842: Add richer group offset reset mechanisms

Thank you for this KIP, +1 (non-binding) -- Ziming > On Jun 15, 2022, at 8:54 PM, hudeqi <16120...@bjtu.edu.cn> wrote: > > Hi all, > > I'd like to start a vote on KIP-842to add some group offset reset mechanisms. > Details can be found here: https://cwiki.apache.org/confluence/x/xhyhD > > Any

[DISCUSS] KIP-849: Expose logdirs total and usable space via kafka-log-dirs.sh

Hi all, I'd like to propose a small KIP to expose logdirs total and usable space via kafka-log-dirs.sh, most of the work has been finished in KIP-827, I just want to show these 2 fields in the output of afka-log-dirs.sh Details can be found here: https://cwiki.apache.org/confluence/display/KAFK

Re: [VOTE] KIP-851: : Add requireStable flag into ListConsumerGroupOffsetsOptions

Thanks for this KIP, we have a kafka-consumer-groups.sh shell which is based on the API you proposed to change, is it worth update it as well? -- Best, Ziming > On Jul 1, 2022, at 9:04 AM, Guozhang Wang wrote: > > Hello folks, > > I'd like to call out for a vote for the following KIP to expos

Re: [ANNOUNCE] New Committer: Chris Egerton

Congratulations Chris ! -- Ziming > On Jul 26, 2022, at 5:01 AM, Matthias J. Sax wrote: > > Congrats! Well deserved! > > -Matthias > > On 7/25/22 1:08 PM, Bill Bejeck wrote: >> Congrats Chris! >> -Bill >> On Mon, Jul 25, 2022 at 3:58 PM Jorge Esteban Quilcate Otoya < >> quilcate.jo...@gmail.c

Re: [DISCUSS] KIP-858: Handle JBOD broker disk failure in KRaft

Hi, Igor, Thanks for this great work, left some questions, 1. We have a version field in meta.properties, currently it’s 1, and we can set it to 2 in this KIP, and we can give an example of server.properties and it’s corresponding meta.properties generated by the storage command tool. 2. When u

Re: [ANNOUNCE] New Kafka PMC Member: A. Sophie Blee-Goldman

Congrats, Sophie! -- Best, Ziming > On Aug 9, 2022, at 3:20 PM, Bruno Cadonna wrote: > > Congrats, Sophie!

Re: About Kafka 2.7.0 source code compilation error

Hello, please use gradlew, for example `./gradlew jar` `./gradlew idea`, or you can use the gradle plugin of IDEA. The `@ nowarn` warn seems to be related to different version of scala and jdk which you can just ignore. > On Feb 18, 2021, at 16:38, 韩可 mailto:han...@cvicse.com>> > wrote: > > H

Re: [ANNOUNCE] New Kafka PMC Member: Chia-Ping Tsai

Congratulations Chia-Ping! > On Mar 13, 2021, at 05:39, Sophie Blee-Goldman > wrote: > > Congrats Chia-Ping! Thanks for all your contributions > > On Fri, Mar 12, 2021 at 12:24 PM Mickael Maison > wrote: > >> Congratulations Chia-Ping! >> >> On Fri, Mar 12, 2021 at 7:54 PM Israel Ekpo wrot

[DISCUSS] KIP-786: Use localhost:9092 as default bootstrap-server/broker-list in client tools

: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191335433 <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191335433> Any comments and feedback are welcome. Thank you. Deng Ziming.

Re: [DISCUSS] KIP-786: Use localhost:9092 as default bootstrap-server/broker-list in client tools

Thank you Maison I have update the KIP number to KIP-789, the url has been updated to: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191335433 <https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191335433> Thanks Deng Ziming > On Oct 31, 2021, at

Re: [VOTE] KIP-778 KRaft upgrades

Hi, David Looking forwarding to this feature +1 (non-binding) Thanks! Ziming Deng > On Dec 11, 2021, at 4:49 AM, David Arthur wrote: > > Hey everyone, I'd like to start a vote for KIP-778 which adds support for > KRaft to KRaft upgrades. > > Notably in this KIP is the first use case of KIP-

Re: [ANNOUNCE] New Kafka PMC member: David Jacot

Congrats David! -- Ziming Deng > On Dec 18, 2021, at 7:08 AM, Gwen Shapira wrote: > > Hi everyone, > > David Jacot has been an Apache Kafka committer since Oct 2020 and has been > contributing to the community consistently this entire time - especially > notable the fact that he reviewed aro

create KIP permission

Could you please grant me access to Create KIP's. thank you, My ID is dengziming

[jira] [Created] (KAFKA-15286) Migrate ApiVersion related code to kraft

Deng Ziming created KAFKA-15286: --- Summary: Migrate ApiVersion related code to kraft Key: KAFKA-15286 URL: https://issues.apache.org/jira/browse/KAFKA-15286 Project: Kafka Issue Type: Task

[jira] [Created] (KAFKA-15287) Change NodeApiVersions.create() to contains both apis of zk and kraft broker

Deng Ziming created KAFKA-15287: --- Summary: Change NodeApiVersions.create() to contains both apis of zk and kraft broker Key: KAFKA-15287 URL: https://issues.apache.org/jira/browse/KAFKA-15287 Project

[jira] [Created] (KAFKA-15288) Change BrokerApiVersionsCommandTest to support kraft mode

Deng Ziming created KAFKA-15288: --- Summary: Change BrokerApiVersionsCommandTest to support kraft mode Key: KAFKA-15288 URL: https://issues.apache.org/jira/browse/KAFKA-15288 Project: Kafka

[jira] [Created] (KAFKA-15289) Use zkBrokerApis.clientApis instead of ApiKeys.zkBrokerApis in most cases

Deng Ziming created KAFKA-15289: --- Summary: Use zkBrokerApis.clientApis instead of ApiKeys.zkBrokerApis in most cases Key: KAFKA-15289 URL: https://issues.apache.org/jira/browse/KAFKA-15289 Project

[jira] [Resolved] (KAFKA-15288) Change BrokerApiVersionsCommandTest to support kraft mode

[ https://issues.apache.org/jira/browse/KAFKA-15288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-15288. - Resolution: Fixed > Change BrokerApiVersionsCommandTest to support kraft m

[jira] [Resolved] (KAFKA-15287) Change NodeApiVersions.create() to contains both apis of zk and kraft broker

[ https://issues.apache.org/jira/browse/KAFKA-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-15287. - Resolution: Fixed > Change NodeApiVersions.create() to contains both apis of zk and kr

[jira] [Created] (KAFKA-15334) DescribeQuorum should not be seen as cluster action

Deng Ziming created KAFKA-15334: --- Summary: DescribeQuorum should not be seen as cluster action Key: KAFKA-15334 URL: https://issues.apache.org/jira/browse/KAFKA-15334 Project: Kafka Issue

[jira] [Created] (KAFKA-15340) Test request quota for kraft controller apis

Deng Ziming created KAFKA-15340: --- Summary: Test request quota for kraft controller apis Key: KAFKA-15340 URL: https://issues.apache.org/jira/browse/KAFKA-15340 Project: Kafka Issue Type

[jira] [Resolved] (KAFKA-15289) Support KRaft mode in RequestQuotaTest

[ https://issues.apache.org/jira/browse/KAFKA-15289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-15289. - Resolution: Fixed > Support KRaft mode in RequestQuotaT

[jira] [Resolved] (KAFKA-13836) Improve KRaft broker heartbeat logic

[ https://issues.apache.org/jira/browse/KAFKA-13836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-13836. - Resolution: Won't Fix > Improve KRaft broker heartbe

[jira] [Created] (KAFKA-15354) Partition leader is not evenly distributed in kraft mode

Deng Ziming created KAFKA-15354: --- Summary: Partition leader is not evenly distributed in kraft mode Key: KAFKA-15354 URL: https://issues.apache.org/jira/browse/KAFKA-15354 Project: Kafka Issue

[jira] [Created] (KAFKA-15371) MetadataShell is stuck when bootstrapping

Deng Ziming created KAFKA-15371: --- Summary: MetadataShell is stuck when bootstrapping Key: KAFKA-15371 URL: https://issues.apache.org/jira/browse/KAFKA-15371 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-15390) FetchResponse.preferredReplica may contains fenced replica in KRaft mode

Deng Ziming created KAFKA-15390: --- Summary: FetchResponse.preferredReplica may contains fenced replica in KRaft mode Key: KAFKA-15390 URL: https://issues.apache.org/jira/browse/KAFKA-15390 Project

[jira] [Resolved] (KAFKA-15286) Migrate ApiVersion related code to kraft

[ https://issues.apache.org/jira/browse/KAFKA-15286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-15286. - Resolution: Fixed > Migrate ApiVersion related code to kr

[jira] [Reopened] (KAFKA-15140) Improve TopicCommandIntegrationTest to be less flaky

[ https://issues.apache.org/jira/browse/KAFKA-15140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming reopened KAFKA-15140: - This is still flaky, it seems the internal topic is also under min isr partitions. https://ci

[jira] [Resolved] (KAFKA-15315) Use getOrDefault rather than get

[ https://issues.apache.org/jira/browse/KAFKA-15315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-15315. - Resolution: Fixed > Use getOrDefault rather than

[jira] [Created] (KAFKA-15566) Klaky tests in FetchRequestTest.scala in KRaft mode

Deng Ziming created KAFKA-15566: --- Summary: Klaky tests in FetchRequestTest.scala in KRaft mode Key: KAFKA-15566 URL: https://issues.apache.org/jira/browse/KAFKA-15566 Project: Kafka Issue Type

[jira] [Created] (KAFKA-15619) Kafka

Deng Ziming created KAFKA-15619: --- Summary: Kafka Key: KAFKA-15619 URL: https://issues.apache.org/jira/browse/KAFKA-15619 Project: Kafka Issue Type: Improvement Affects Versions: 3.5.1

[jira] [Resolved] (KAFKA-15390) FetchResponse.preferredReplica may contains fenced replica in KRaft mode

[ https://issues.apache.org/jira/browse/KAFKA-15390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-15390. - Fix Version/s: 3.6.0 Resolution: Fixed > FetchResponse.preferredReplica may conta

[jira] [Resolved] (KAFKA-13005) Support JBOD in kraft mode

[ https://issues.apache.org/jira/browse/KAFKA-13005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-13005. - Resolution: Duplicate > Support JBOD in kraft m

[jira] [Resolved] (KAFKA-15619) Deleted topics will come back again

[ https://issues.apache.org/jira/browse/KAFKA-15619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-15619. - Assignee: Deng Ziming Resolution: Invalid This has been fixed after setting

[jira] [Created] (KAFKA-16181) Use incrementalAlterConfigs when updating broker configs by kafka-configs.sh

Deng Ziming created KAFKA-16181: --- Summary: Use incrementalAlterConfigs when updating broker configs by kafka-configs.sh Key: KAFKA-16181 URL: https://issues.apache.org/jira/browse/KAFKA-16181 Project

[jira] [Resolved] (KAFKA-14378) consumer should refresh preferred read replica on update metadata

[ https://issues.apache.org/jira/browse/KAFKA-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-14378. - Resolution: Duplicate duplicated with KAFKA-14379 > consumer should refresh preferred r

[jira] [Resolved] (KAFKA-14380) consumer should refresh preferred read replica on metadata update

[ https://issues.apache.org/jira/browse/KAFKA-14380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-14380. - Resolution: Duplicate duplicated with KAFKA-14379 > consumer should refresh preferred r

[jira] [Resolved] (KAFKA-14689) Kafka won't start on Windows in KRaft mode

[ https://issues.apache.org/jira/browse/KAFKA-14689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-14689. - Resolution: Duplicate This is the same with KAFKA-14273 > Kafka won't start on Wi

[jira] [Reopened] (KAFKA-14291) KRaft: ApiVersionsResponse doesn't have finalizedFeatures and finalizedFeatureEpoch in KRaft mode

[ https://issues.apache.org/jira/browse/KAFKA-14291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming reopened KAFKA-14291: - Assignee: Deng Ziming > KRaft: ApiVersionsResponse doesn't have finalizedFeat

[jira] [Created] (KAFKA-14989) Flaky test TransactionsTest.testFailureToFenceEpoch

Deng Ziming created KAFKA-14989: --- Summary: Flaky test TransactionsTest.testFailureToFenceEpoch Key: KAFKA-14989 URL: https://issues.apache.org/jira/browse/KAFKA-14989 Project: Kafka Issue Type

[jira] [Created] (KAFKA-15036) Kraft leader change fails when invoking getFinalizedFeatures

Deng Ziming created KAFKA-15036: --- Summary: Kraft leader change fails when invoking getFinalizedFeatures Key: KAFKA-15036 URL: https://issues.apache.org/jira/browse/KAFKA-15036 Project: Kafka

[jira] [Created] (KAFKA-15065) ApiVersionRequest is not properly handled in Sasl ControllerServer

Deng Ziming created KAFKA-15065: --- Summary: ApiVersionRequest is not properly handled in Sasl ControllerServer Key: KAFKA-15065 URL: https://issues.apache.org/jira/browse/KAFKA-15065 Project: Kafka

[jira] [Resolved] (KAFKA-15036) Kraft leader change fails when invoking getFinalizedFeatures

[ https://issues.apache.org/jira/browse/KAFKA-15036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-15036. - Resolution: Fixed > Kraft leader change fails when invoking getFinalizedFeatu

[jira] [Created] (KAFKA-18101) Merge duplicate assertFutureThrows and assertFutureExceptionTypeEquals

Deng Ziming created KAFKA-18101: --- Summary: Merge duplicate assertFutureThrows and assertFutureExceptionTypeEquals Key: KAFKA-18101 URL: https://issues.apache.org/jira/browse/KAFKA-18101 Project: Kafka

[jira] [Resolved] (KAFKA-13788) Creation of invalid dynamic config prevents further creation of valid configs

[ https://issues.apache.org/jira/browse/KAFKA-13788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-13788. - Fix Version/s: 4.0.0 Resolution: Duplicate duplication of KAFKA-16181 > Creation

[jira] [Resolved] (KAFKA-16181) Use incrementalAlterConfigs when updating broker configs by kafka-configs.sh

[ https://issues.apache.org/jira/browse/KAFKA-16181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-16181. - Fix Version/s: 4.0.0 Resolution: Resolved > Use incrementalAlterConfigs when updat

[jira] [Resolved] (KAFKA-18070) Update kafka-metadata-quorum.sh output in docs to match post-KIP-853 appearance

[ https://issues.apache.org/jira/browse/KAFKA-18070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-18070. - Reviewer: Deng Ziming Resolution: Fixed > Update kafka-metadata-quorum.sh output in d

[jira] [Resolved] (KAFKA-12903) Replace producer state entry with auto-generated protocol

[ https://issues.apache.org/jira/browse/KAFKA-12903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-12903. - Resolution: Duplicate Already fixed in KAFKA-17056 > Replace producer state entry with a