Re: [DISCUSS] Git commits and metadata

Hi David, I like the motivation for this change but I have some suggestions. 1. To me the only required fields should be "reviewed-by" and "approved-by". I don't fully understand the rest of the fields. I would like to limit the burden on the committer to merge a change. 2. How about extending "a

Re: [DISCUSS] Apache Kafka 3.9.1 release

Thanks Luke, Sounds like a good plan. I just added three more tickets that I would like to include in the release. Can you give a more concrete date when you want to create the first RC? Having a concrete date (even if if might shift a little bit), is usually more helpful for people to plan

Re: [DISCUSS] Apache Kafka 3.9.1 release

Hi Matthias, Thanks for your suggestion. The code freeze date will be *9 April 2025 *(Wednesday). I've also updated the release plan page. Thanks. Luke On Thu, Mar 27, 2025 at 2:15 AM Matthias J. Sax wrote: > Thanks Luke, > > Sounds like a good plan. I just added three more tickets that I woul

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

See

Re: [DISCUSS] Git commits and metadata

Hi David, In general, I'm in favor of adding information where reasonably possible. How are these header values populated by the merging committer? Magic or manual? I agree with others that adding so many additional "*-by" headers could be confusing, leading to inconsistent usage. Is the equiva

Re: 回复： [DISCUSS] KIP-1134: Virtual Clusters in Kafka

Hi all, I'm coming around to this design now. If we require users in some cluster (the root cluster) to be able to refer to resources in virtual clusters for administration, and are not willing to add protocol-specific support for this, it needs to be done through name generation of some kind. I

[jira] [Created] (KAFKA-19028) AlterConfigPolicy with OpType.DELETE : inconsistent behavior between TOPIC and BROKER resource

Edoardo Comar created KAFKA-19028: - Summary: AlterConfigPolicy with OpType.DELETE : inconsistent behavior between TOPIC and BROKER resource Key: KAFKA-19028 URL: https://issues.apache.org/jira/browse/KAFKA-19028

[VOTE] KIP-1133: AK Documentation and Website in Markdown

Hey all I would like to call a vote on KIP-1133: AK Documentation and Website in Markdown. KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-1133%3A+AK+Documentation+and+Website+in+Markdown Discussion thread: https://lists.apache.org/thread/kc0kg0dxy6xdrwyv10k56k6g058ng2dw Regards Hari

Fetch Request performing remote KIP-405 reads gotcha

Hey all, I was doing a deep dive on the internals of KIP-405's read path and I was surprised to learn that the broker only fetches remote data for ONE partition in a given FetchRequest. In other words, if a consumer sends a FetchRequest requesting 50 topic-partitions, and each partition's requeste

[jira] [Created] (KAFKA-19047) Broker registrations are slow if previously fenced or shutdown

Alyssa Huang created KAFKA-19047: Summary: Broker registrations are slow if previously fenced or shutdown Key: KAFKA-19047 URL: https://issues.apache.org/jira/browse/KAFKA-19047 Project: Kafka

Re: [DISCUSS] KIP-1131: Controller-side monitoring for broker shutdown and startup

Hi Kevin, thanks for the KIP. I have a couple of questions/considerations. If I understand correctly unfenced == active. In the code we always use the term active, so I think it would be better to use that for the state 0 description. You propose creating per-broker metrics indicating their state

[jira] [Resolved] (KAFKA-18899) Limit retry time for ShareConsumer.commitAsync

[ https://issues.apache.org/jira/browse/KAFKA-18899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18899. -- Resolution: Fixed > Limit retry time for ShareConsumer.commitAsync > -

[jira] [Resolved] (KAFKA-18612) Update ApiMessageFormatter

[ https://issues.apache.org/jira/browse/KAFKA-18612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-18612. - Fix Version/s: 4.1.0 Resolution: Fixed Addressed by https://github.com/apache/kafka/comm

[jira] [Resolved] (KAFKA-18300) Improve coordinator records

[ https://issues.apache.org/jira/browse/KAFKA-18300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-18300. - Fix Version/s: 4.1.0 Resolution: Fixed > Improve coordinator records > --

Re: [DISCUSS] Git commits and metadata

Hi David, I am in favor of having a separate field for the people who approve the PR vs the ones who leave some comments. I actually brought this up when I initially joined the community (probably around a decade ago), but it didn't resonate at the time. :) It also makes sense to use a consistent

[jira] [Created] (KAFKA-19046) Change delete cleanup policy to compact cleanup policy

George Yang created KAFKA-19046: --- Summary: Change delete cleanup policy to compact cleanup policy Key: KAFKA-19046 URL: https://issues.apache.org/jira/browse/KAFKA-19046 Project: Kafka Issue Ty

Re: Fetch Request performing remote KIP-405 reads gotcha

Hi Stanislav, Thanks for raising this! I totally forgot about it! For the documentation improvement, I think more is better. All you listed above can be done together. Also "remote.fetch.max.wait.ms" config is also a good place to add this missing info. Thanks. Luke On Thu, Mar 27, 2025 at 4:27

[jira] [Created] (KAFKA-19048) Minimal Movement Replica Balancing algorithm

Jialun Peng created KAFKA-19048: --- Summary: Minimal Movement Replica Balancing algorithm Key: KAFKA-19048 URL: https://issues.apache.org/jira/browse/KAFKA-19048 Project: Kafka Issue Type: Improv