[jira] [Resolved] (KAFKA-18200) New coordinator can flush an empty batch if append fails

[ https://issues.apache.org/jira/browse/KAFKA-18200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-18200. - Resolution: Fixed > New coordinator can flush an empty batch if append fails > -

[jira] [Created] (KAFKA-18281) Kafka (3.9.0) is improperly validating non-advertised listeners for routable controller addresses

Justin Lee created KAFKA-18281: -- Summary: Kafka (3.9.0) is improperly validating non-advertised listeners for routable controller addresses Key: KAFKA-18281 URL: https://issues.apache.org/jira/browse/KAFKA-18281

[jira] [Created] (KAFKA-18280) fix e2e TestSecurityRollingUpgrade.test_rolling_upgrade_sasl_mechanism_phase_one

TaiJuWu created KAFKA-18280: --- Summary: fix e2e TestSecurityRollingUpgrade.test_rolling_upgrade_sasl_mechanism_phase_one Key: KAFKA-18280 URL: https://issues.apache.org/jira/browse/KAFKA-18280 Project: Kafka

[jira] [Created] (KAFKA-18279) add JDK 11 check and test for clients and streams module

Chia-Ping Tsai created KAFKA-18279: -- Summary: add JDK 11 check and test for clients and streams module Key: KAFKA-18279 URL: https://issues.apache.org/jira/browse/KAFKA-18279 Project: Kafka

[jira] [Created] (KAFKA-18278) the name and description of `run-gradle` is incorrect

Chia-Ping Tsai created KAFKA-18278: -- Summary: the name and description of `run-gradle` is incorrect Key: KAFKA-18278 URL: https://issues.apache.org/jira/browse/KAFKA-18278 Project: Kafka Iss

Re: New release branch 4.0

hi David Are we planning to move AsyncConsumer to production in version 4.0.0? If not, can we assume that AsyncConsumer-related issues will be deferred to next release ? For example: https://issues.apache.org/jira/browse/KAFKA-18034 Best, Chia-Ping On 2024/12/16 15:47:47 David Jacot wrote: > H

[jira] [Created] (KAFKA-18277) fix e2e network_degrade_test

TaiJuWu created KAFKA-18277: --- Summary: fix e2e network_degrade_test Key: KAFKA-18277 URL: https://issues.apache.org/jira/browse/KAFKA-18277 Project: Kafka Issue Type: Test Reporter: Tai

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.9 #127

See

[jira] [Resolved] (KAFKA-17418) Fix the incorrect markdown of junit.py caused by newline character

[ https://issues.apache.org/jira/browse/KAFKA-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-17418. Resolution: Fixed > Fix the incorrect markdown of junit.py caused by newline character > -

[jira] [Resolved] (KAFKA-16096) Drop broker and tools support for Java 11 in Kafka 4.0 (deprecate in 3.7) (KIP-1013)

[ https://issues.apache.org/jira/browse/KAFKA-16096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16096. Resolution: Fixed all sub-tasks are completed > Drop broker and tools support for Java 11

[jira] [Created] (KAFKA-18276) Migrate RebootstrapTest to new test infra

Chia-Ping Tsai created KAFKA-18276: -- Summary: Migrate RebootstrapTest to new test infra Key: KAFKA-18276 URL: https://issues.apache.org/jira/browse/KAFKA-18276 Project: Kafka Issue Type: Imp

[jira] [Resolved] (KAFKA-18237) add 3.7.2 to code base

[ https://issues.apache.org/jira/browse/KAFKA-18237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] TengYao Chi resolved KAFKA-18237. - Resolution: Fixed > add 3.7.2 to code base > -- > > Key: KAF

[jira] [Created] (KAFKA-18275) Restarting broker in testing should use the same port

Chia-Ping Tsai created KAFKA-18275: -- Summary: Restarting broker in testing should use the same port Key: KAFKA-18275 URL: https://issues.apache.org/jira/browse/KAFKA-18275 Project: Kafka Iss

[jira] [Created] (KAFKA-18274) Failed to restart controller in testing due to closed socket channel

Chia-Ping Tsai created KAFKA-18274: -- Summary: Failed to restart controller in testing due to closed socket channel Key: KAFKA-18274 URL: https://issues.apache.org/jira/browse/KAFKA-18274 Project: Kaf

Re: [DISCUSS] Java 23 Support for 3.9.x

Hi Greg, Thanks for raising this. My main question is: Is Kafka v3.9 a LTS release? It seems many people think it is, but I never see this kind of discussion anywhere. In Kafka, IIRC, we have never had this kind of LTS release before. We need to clearly define the meaning of LTS release for v3.9.x

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.8 #121

See

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

See

Re: [VOTE] KIP-1101: Trigger rebalance on rack topology changes

+1 （non-binding） On Mon, Dec 16, 2024 at 5:01 PM PoAn Yang wrote: > Hi All, > > I would like to start vote on KIP-1101: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1101%3A+Trigger+rebalance+on+rack+topology+changes > > Discussion thread: > https://lists.apache.org/thread/l8ko353v3n

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.9 #126

See

[jira] [Created] (KAFKA-18273) Implement kafka-share-groups.sh --describe --verbose

Andrew Schofield created KAFKA-18273: Summary: Implement kafka-share-groups.sh --describe --verbose Key: KAFKA-18273 URL: https://issues.apache.org/jira/browse/KAFKA-18273 Project: Kafka

Re: [DISCUSS] KIP-1101: Trigger rebalance on rack topology changes

Hi PoAn, Thanks for the KIP. AS1: From the point of view of share groups, the API and record schema definitions are unstable in AK 4.0. In AK 4.1, we will start supporting proper versioning. As a result, I think you do not need to deprecate the fields in the ShareGroupPartitionMetadataValue. Just

[jira] [Created] (KAFKA-18272) Deprecated protocol api usage should be logged at info level

Ismael Juma created KAFKA-18272: --- Summary: Deprecated protocol api usage should be logged at info level Key: KAFKA-18272 URL: https://issues.apache.org/jira/browse/KAFKA-18272 Project: Kafka I

[jira] [Created] (KAFKA-18271) Trigger CI when a PR is marked "ready for review"

David Arthur created KAFKA-18271: Summary: Trigger CI when a PR is marked "ready for review" Key: KAFKA-18271 URL: https://issues.apache.org/jira/browse/KAFKA-18271 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-18270) SaslHandshake v0 incorrectly tagged as deprecated

Ismael Juma created KAFKA-18270: --- Summary: SaslHandshake v0 incorrectly tagged as deprecated Key: KAFKA-18270 URL: https://issues.apache.org/jira/browse/KAFKA-18270 Project: Kafka Issue Type: S

[jira] [Created] (KAFKA-18269) Remove deprecated protocol APIs support in 4.0

Ismael Juma created KAFKA-18269: --- Summary: Remove deprecated protocol APIs support in 4.0 Key: KAFKA-18269 URL: https://issues.apache.org/jira/browse/KAFKA-18269 Project: Kafka Issue Type: Sub-

requesting permissions to contribute to Apache Kafka

JIRA id: soji Wiki id: soji

Re: [VOTE] KIP-1109: Unifying Kafka Consumer Topic Metrics

Hi, Apoorv, Thanks for the KIP. +1 Jun On Thu, Dec 12, 2024 at 4:26 PM Apoorv Mittal wrote: > Hi All, > I would like to start vote on KIP-1109: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1109%3A+Unifying+Kafka+Consumer+Topic+Metrics > > Discussion thread: > https://lists.apache.

[jira] [Resolved] (KAFKA-18259) Documentation for consumer auto.offset.reset contains invalid HTML

[ https://issues.apache.org/jira/browse/KAFKA-18259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18259. -- Fix Version/s: 4.0.0 Resolution: Fixed > Documentation for consumer auto.offset

[jira] [Resolved] (KAFKA-18263) Group lock must be acquired when reverting static membership rejoin

[ https://issues.apache.org/jira/browse/KAFKA-18263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-18263. - Fix Version/s: 4.0.0 3.9.1 Resolution: Fixed > Group lock must be acqu

Re: [DISCUSS] Java 23 Support for 3.9.x

Hi all, Another downstream project has reported upgrade difficulties because of our Java support policy: https://github.com/quarkusio/quarkus/issues/39634 Thanks, Greg On Tue, Dec 3, 2024 at 7:33 AM Chia-Ping Tsai wrote: > hi all, > > I believe this is an NP-hard challenge because we aim to re

[jira] [Created] (KAFKA-18268) Add metric for log cleaner thread busy percentage

Divij Vaidya created KAFKA-18268: Summary: Add metric for log cleaner thread busy percentage Key: KAFKA-18268 URL: https://issues.apache.org/jira/browse/KAFKA-18268 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-1101: Trigger rebalance on rack topology changes

hi David > DJ05 One of the benefits of having a single hash per group (DJ04) is the reduction in the size of stored data. Additionally, the cost of re-computing can be minimized thanks to caching. So I'm + 1 to DJ04. However, the advantage of storing the topic cache in the metadata image is so

[jira] [Created] (KAFKA-18267) Add test for CloseOption

TengYao Chi created KAFKA-18267: --- Summary: Add test for CloseOption Key: KAFKA-18267 URL: https://issues.apache.org/jira/browse/KAFKA-18267 Project: Kafka Issue Type: Test Reporter:

[jira] [Resolved] (KAFKA-18226) Disable CustomQuotaCallbackTest and remove `isKRaftTest`

[ https://issues.apache.org/jira/browse/KAFKA-18226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-18226. Fix Version/s: 4.0.0 Resolution: Fixed > Disable CustomQuotaCallbackTest and remove

New release branch 4.0

Hello Kafka developers and friends, As promised, we now have a release branch for 4.0 release. Trunk has been bumped to 4.1.0-SNAPSHOT. I'll be going over the JIRAs to move every non-blocker from this release to the next release. >From this point, most changes should go to trunk. - Blockers (exi

[jira] [Created] (KAFKA-18266) Re-order validation for TimeIndex sanity

Divij Vaidya created KAFKA-18266: Summary: Re-order validation for TimeIndex sanity Key: KAFKA-18266 URL: https://issues.apache.org/jira/browse/KAFKA-18266 Project: Kafka Issue Type: Improvem

Re: [DISCUSS] KIP-1092: Extend Consumer#close with an option to leave the group or not

Hi everyone, I'd like to discuss the leave callback implementation. While this KIP focuses on sending leave requests, we should also consider how to handle the leave callback. IMHO, we should maintain the original logic: if a consumer remains in the group, the callback should not be invoked. What

[jira] [Resolved] (KAFKA-18018) Consumption degrading when using DefaultStatePersister for 1 million records of size 1KB

[ https://issues.apache.org/jira/browse/KAFKA-18018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Dixit resolved KAFKA-18018. --- Resolution: Later > Consumption degrading when using DefaultStatePersister for 1 million rec

[PR] [MINOR] Add Andrew to committers [kafka-site]

AndrewJSchofield opened a new pull request, #654: URL: https://github.com/apache/kafka-site/pull/654 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubsc

[jira] [Created] (KAFKA-18265) Optimizing SharePartition locking to improve fetch speed

Abhinav Dixit created KAFKA-18265: - Summary: Optimizing SharePartition locking to improve fetch speed Key: KAFKA-18265 URL: https://issues.apache.org/jira/browse/KAFKA-18265 Project: Kafka Is

Re: [VOTE] KIP-1118: Add Deadlock Protection on Producer Network Thread

+1 (binding) From: TaiJu Wu Sent: 16 December 2024 09:41 To: dev@kafka.apache.org Subject: Re: [VOTE] KIP-1118: Add Deadlock Protection on Producer Network Thread +1（non-binding) On Mon, Dec 16, 2024 at 5:41 PM Chia-Ping Tsai wrote: > +1 (binding) > > 郭骏旺 於

Re: [DISCUSS] KIP-1101: Trigger rebalance on rack topology changes

Hi PoAn, Thanks for the KIP. I have some comments about it. DJ01: Please, remove all the code from the KIP. We only care about public interface changes, not about implementation details. DJ02: Regarding the hash computation, I agree that we should use Murmur3. However, I don't quite like the impl

[jira] [Resolved] (KAFKA-18247) Use log4j2 yaml to rewrite the fix of KAFKA-18145

[ https://issues.apache.org/jira/browse/KAFKA-18247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18247. Fix Version/s: 4.0.0 Resolution: Fixed > Use log4j2 yaml to rewrite the fix of KAFK

Re: [DISCUSS] Apache Kafka 4.0.0 release

Hey David About KIP 1030 [1], we have 4 PRs open. They are stuck at flaky/failing tests which the author is fixing. We will target to merge them this week. [1] https://cwiki.apache.org/confluence/display/KAFKA/KIP-1030%3A+Change+constraints+and+default+values+for+various+configurations -- Divij

RE: [VOTE] KIP-1118: Add Deadlock Protection on Producer Network Thread

+1 (non-binding)

Re: [VOTE] KIP-1118: Add Deadlock Protection on Producer Network Thread

+1（non-binding) On Mon, Dec 16, 2024 at 5:41 PM Chia-Ping Tsai wrote: > +1 (binding) > > 郭骏旺 於 2024年12月16日 週一 上午9:16寫道： > > > +1 (non-binding) > > > > On Mon, Dec 9, 2024 at 10:33 AM TengYao Chi wrote: > > > > > Hi everyone, > > > > > > Based on our discussion > > >

Re: [VOTE] KIP-1118: Add Deadlock Protection on Producer Network Thread

+1 (binding) 郭骏旺 於 2024年12月16日 週一 上午9:16寫道： > +1 (non-binding) > > On Mon, Dec 9, 2024 at 10:33 AM TengYao Chi wrote: > > > Hi everyone, > > > > Based on our discussion > > > > regarding > > KIP-1118 > > < > > > https://cwiki.ap

Re: [VOTE] KIP-1101: Trigger rebalance on rack topology changes

Hi Chia-Ping, Thanks for the vote and reminder. I update the KIP for it. Regards, PoAn > On Dec 16, 2024, at 5:19 PM, TaiJu Wu wrote: > > +1 （non-binding） > > On Mon, Dec 16, 2024 at 5:01 PM PoAn Yang wrote: > >> Hi All, >> >> I would like to start vote on KIP-1101: >> >> https://cwiki.ap

[jira] [Created] (KAFKA-18264) Remove NotLeaderForPartitionException

Chia-Ping Tsai created KAFKA-18264: -- Summary: Remove NotLeaderForPartitionException Key: KAFKA-18264 URL: https://issues.apache.org/jira/browse/KAFKA-18264 Project: Kafka Issue Type: Improve

Re: [VOTE] KIP-1101: Trigger rebalance on rack topology changes

+1 （non-binding） On Mon, Dec 16, 2024 at 5:01 PM PoAn Yang wrote: > Hi All, > > I would like to start vote on KIP-1101: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1101%3A+Trigger+rebalance+on+rack+topology+changes > > Discussion thread: > https://lists.apache.org/thread/l8ko353v3n

Re: [VOTE] KIP-1101: Trigger rebalance on rack topology changes

+1 (binding) nit: could you append the "cache mechanism" to the description "The second way only needs to recalculate expired topic hash."? The cache is another strong reason for choosing the second approach. Best, Chia-Ping PoAn Yang 於 2024年12月16日 週一 下午5:00寫道： > Hi All, > > I would like to st

[VOTE] KIP-1101: Trigger rebalance on rack topology changes

Hi All, I would like to start vote on KIP-1101: https://cwiki.apache.org/confluence/display/KAFKA/KIP-1101%3A+Trigger+rebalance+on+rack+topology+changes Discussion thread: https://lists.apache.org/thread/l8ko353v3nn1blgymsty895x6c98oxlx Thanks, PoAn

[jira] [Created] (KAFKA-18263) Group lock must be acquired when reverting static membership rejoin

David Jacot created KAFKA-18263: --- Summary: Group lock must be acquired when reverting static membership rejoin Key: KAFKA-18263 URL: https://issues.apache.org/jira/browse/KAFKA-18263 Project: Kafka

Re: [DISCUSS] KIP-1034: Dead letter queue in Kafka Streams

BC9: Thinking about the two options, I prefer the last solution. Introducing a new enum Result allows us to use RESUME instead of CONTINUE cleanly, without causing source compatibility issues. It also appears to be the most forward-compatible and maintainable approach, as it avoids the complexit

[jira] [Resolved] (KAFKA-17934) Add duration based offset reset option for consumer clients

[ https://issues.apache.org/jira/browse/KAFKA-17934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-17934. -- Resolution: Fixed > Add duration based offset reset option for consumer clients >

[jira] [Resolved] (KAFKA-18014) Add duration based offset reset option for ShareConsumer

[ https://issues.apache.org/jira/browse/KAFKA-18014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18014. -- Resolution: Fixed > Add duration based offset reset option for ShareConsumer > ---

Re: [DISCUSS] Apache Kafka 4.0.0 release

Hi Chia-Ping, Regarding KAFKA-18225, I agree that it is an issue that we must fix in 4.0. I see that Colin's already commented in the Jira about the suggested way forward. I agree with the proposal. Thanks, David On Fri, Dec 13, 2024 at 6:22 PM Chia-Ping Tsai wrote: > hi DJ > > I have merged t