[DISCUSS] KIP-660: Pluggable ReplicaPlacer

Hi, I'd like to start a new discussion on KIP-660. I originally wrote this KIP in 2020 and the initial discussion (https://lists.apache.org/thread/xn7xyb74nyt281brto4x28r9rzxm4lp9) raised some concerns especially around KRaft (which did not exist at that time) and scalability. Since then, we got

Re: [DISCUSS] KIP-820: Extend KStream process with new Processor API

Thanks, Matthias. KIP is updated with the APIs. On Tue, 15 Mar 2022 at 23:28, Matthias J. Sax wrote: > Thanks. > > It would be good to add the concrete interfaces of the new classed to > the KIP, ie, > > - FixedKeyProcessorSupplier > - FixedKeyProcessor > - FixedKeyProcessorContext > -

[jira] [Created] (KAFKA-13752) Using `equals` instead of `==` when Uuid compare in Java

Xiaobing Fang created KAFKA-13752: - Summary: Using `equals` instead of `==` when Uuid compare in Java Key: KAFKA-13752 URL: https://issues.apache.org/jira/browse/KAFKA-13752 Project: Kafka

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.1 #89

See Changes: -- [...truncated 503725 lines...] [2022-03-17T19:03:43.567Z] > Task :core:classes UP-TO-DATE [2022-03-17T19:03:43.567Z] > Task :core:compileTestJava NO-SOURCE

Re: [DISCUSS] KIP-794: Strictly Uniform Sticky Partitioner

Hi all, Thank you to everybody who contributed to this discussion, we've come a long way and now the "rejected alternatives" section is almost as big as the actual proposal (which indicates that it's a well thought through solution :-)). If there are no further considerations, I'll start voting

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #779

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.0 #189

See

[jira] [Created] (KAFKA-13754) Follower should reject Fetch request while the leader is recovering

Jose Armando Garcia Sancio created KAFKA-13754: -- Summary: Follower should reject Fetch request while the leader is recovering Key: KAFKA-13754 URL: https://issues.apache.org/jira/browse/KAFKA-13754

Re: [VOTE] KIP-653: Upgrade log4j to log4j2

Hi all, The KIP compatibility section does not include enough detail. I am puzzled how we voted +1 given that. I noticed that Colin indicated it would only be acceptable in a major release unless the new version was fully compatible (which it is not). Can we clarify what we actually voted for

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #780

See

[jira] [Created] (KAFKA-13753) Log cleaner should transaction metadata in index until corresponding marker is removed

Jason Gustafson created KAFKA-13753: --- Summary: Log cleaner should transaction metadata in index until corresponding marker is removed Key: KAFKA-13753 URL: https://issues.apache.org/jira/browse/KAFKA-13753

[jira] [Resolved] (KAFKA-7077) KIP-318: Make Kafka Connect Source idempotent

[ https://issues.apache.org/jira/browse/KAFKA-7077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-7077. -- Resolution: Fixed > KIP-318: Make Kafka Connect Source idempotent >

Re: [DISCUSS] KIP-660: Pluggable ReplicaPlacer

Thanks Mickael, this makes sense to me! I've been wanting something like this in order to decommission a broker without new partitions getting accidentally assigned to it. Ryanne On Thu, Mar 17, 2022, 5:56 AM Mickael Maison wrote: > Hi, > > I'd like to start a new discussion on KIP-660. I

[jira] [Resolved] (KAFKA-13744) Quota metric tags are inconsistent

[ https://issues.apache.org/jira/browse/KAFKA-13744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Esteban Quilcate Otoya resolved KAFKA-13744. -- Resolution: Not A Problem > Quota metric tags are

[jira] [Resolved] (KAFKA-13742) Quota byte-rate/request metrics are loaded only when at least one quota is register

[ https://issues.apache.org/jira/browse/KAFKA-13742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Esteban Quilcate Otoya resolved KAFKA-13742. -- Resolution: Not A Problem Given that I got a better

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #781

See

[jira] [Resolved] (KAFKA-13136) kafka-connect task.max : active task in consumer group is limited by the bigger topic to consume

[ https://issues.apache.org/jira/browse/KAFKA-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-13136. --- Resolution: Fixed > kafka-connect task.max : active task in consumer group is limited by

[jira] [Resolved] (KAFKA-13509) Support max timestamp in GetOffsetShell

[ https://issues.apache.org/jira/browse/KAFKA-13509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13509. - Reviewer: David Jacot Resolution: Fixed > Support max timestamp in GetOffsetShell >

[jira] [Resolved] (KAFKA-13750) Client Compatability KafkaTest uses invalid idempotency configs

[ https://issues.apache.org/jira/browse/KAFKA-13750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13750. - Fix Version/s: 3.2.0 3.1.1 3.0.2 Resolution: Fixed

Re: [VOTE] KIP-820: Extend KStream process with new Processor API

Reviewed the updated docs, and recasting my +1 vote again, thanks Jorge for pushing it through! Guozhang On Tue, Mar 15, 2022 at 4:28 PM Matthias J. Sax wrote: > +1 (binding) > > Thanks for pushing this through. Was a difficult discussion! > > > -Matthias > > On 3/15/22 10:01 AM, John Roesler