[jira] [Resolved] (KAFKA-18745) Handle the disconnected inter broker RPC calls within the persister

[ https://issues.apache.org/jira/browse/KAFKA-18745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18745. -- Resolution: Fixed > Handle the disconnected inter broker RPC calls within the persiste

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

Hello, I'm planning to initiate a vote on this KIP next week. In the meantime, please share any further questions or comments you may have. Regards, Harish On Tue, Mar 11, 2025 at 7:42 AM David Arthur wrote: > TaiJuWu, > > Hugo has a Docker image which makes it very easy to run locally, and I

[jira] [Created] (KAFKA-19015) Remove share session from cache on connection drop

Andrew Schofield created KAFKA-19015: Summary: Remove share session from cache on connection drop Key: KAFKA-19015 URL: https://issues.apache.org/jira/browse/KAFKA-19015 Project: Kafka Is

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

See

Re: [DISCUSS] KIP-1140: Avoid to return null value in Map from public api of consumer

> > 2. Given that clients in 4.0 support brokers with version 2.1 or higher, > `offsetsForTimes` should never return maps with `null` values (check the > javadoc for the details of when this happens). We can perhaps consider this > a documentation fix (versus a behavior change). > Thinking about t

Re: [VOTE] KIP-1064 - Upgrade slf4j to 2.x

Hi Chia-Ping, I don't think we're in the business of shipping multiple logging libraries. Here's my take: 1. We should pick one logging library for services/servers, ship it and include a configuration file for it. 2. For clients, we leave it to the users to select the logging library - clients r

[jira] [Created] (KAFKA-19014) Potential race condition in remote-log-reader and remote-log-index-cleaner thread

Hasil Sharma created KAFKA-19014: Summary: Potential race condition in remote-log-reader and remote-log-index-cleaner thread Key: KAFKA-19014 URL: https://issues.apache.org/jira/browse/KAFKA-19014 Pro

[PR] Uploaded Unistam logo [kafka-site]

varunprakashnkl opened a new pull request, #677: URL: https://github.com/apache/kafka-site/pull/677 (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 unsubscr

[PR] Update powered-by.html [kafka-site]

varunprakashnkl opened a new pull request, #676: URL: https://github.com/apache/kafka-site/pull/676  Added Unistam -- This is an automated message from the Apache Git Service. To respond to t

[jira] [Resolved] (KAFKA-18975) Move clients-integration-test out of core module

[ https://issues.apache.org/jira/browse/KAFKA-18975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18975. Fix Version/s: 4.1.0 Resolution: Fixed > Move clients-integration-test out of core

[jira] [Reopened] (KAFKA-18776) Flaky testMarkCoordinatorUnknownLoggingAccuracy

[ https://issues.apache.org/jira/browse/KAFKA-18776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur reopened KAFKA-18776: -- The flakiness has regressed https://develocity.apache.org/scans/tests?search.relativeStartTime=P2

Re: [DISCUSS] KIP-1140: Avoid to return null value in Map from public api of consumer

Hi Jiunn-Yang, Response inline... On Wed, Mar 19, 2025, at 5:28 AM, 黃竣陽 wrote: > Hello Kirk True, > > Thanks for your comments. > > KT1: In fact, while reviewing projects on GitHub, I haven't found any that > would be affected by this change. Most developers simply retrieve the Long > value f

[jira] [Resolved] (KAFKA-17431) KRaft servers require valid static socketserver configuration to start

[ https://issues.apache.org/jira/browse/KAFKA-17431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Wu resolved KAFKA-17431. -- Fix Version/s: 4.1.0 Resolution: Fixed > KRaft servers require valid static socketserver config

[jira] [Resolved] (KAFKA-18792) Enforce uniform PR structure for merge queue

[ https://issues.apache.org/jira/browse/KAFKA-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur resolved KAFKA-18792. -- Resolution: Fixed > Enforce uniform PR structure for merge queue > ---

Re: [DISCUSS] Apache Kafka 4.1.0 release

Thanks Mickael! Ismael On Wed, Mar 19, 2025, 5:54 AM David Arthur wrote: > +1 thanks Mickael! > > David Arthur > > > On Wed, Mar 19, 2025 at 07:59 Mickael Maison > wrote: > > > Hi, > > > > I'd like to volunteer to be the release manager for the Apache Kafka > > 4.1.0 release. > > > > If there

Re: [DISCUSS] Apache Kafka 4.1.0 release

Thanks to Mickael for taking this over!!! Best, Chia-Ping On 2025/03/19 11:58:37 Mickael Maison wrote: > Hi, > > I'd like to volunteer to be the release manager for the Apache Kafka > 4.1.0 release. > > If there are no objections, I'll start building the release plan in > the next few days. >

[jira] [Created] (KAFKA-19012) Messages ending up on the wrong topic

Donny Nadolny created KAFKA-19012: - Summary: Messages ending up on the wrong topic Key: KAFKA-19012 URL: https://issues.apache.org/jira/browse/KAFKA-19012 Project: Kafka Issue Type: Bug A

[DISCUSS] Apache Kafka 4.1.0 release

Hi, I'd like to volunteer to be the release manager for the Apache Kafka 4.1.0 release. If there are no objections, I'll start building the release plan in the next few days. Thanks, Mickael

[jira] [Created] (KAFKA-19011) Improve EndToEndLatency

Chia-Ping Tsai created KAFKA-19011: -- Summary: Improve EndToEndLatency Key: KAFKA-19011 URL: https://issues.apache.org/jira/browse/KAFKA-19011 Project: Kafka Issue Type: Improvement

Re: 3.9.1 bug-fix release?

Thanks Luke! Highly appreciated! Looking forward to learn about the release plan and timeline as a first step. -Matthias On 3/19/25 9:31 AM, Chia-Ping Tsai wrote: Luke is a hero to 3.x users! Best, Chia-Ping Ismael Juma 於 2025年3月19日 週三 下午12:00寫道： Thanks Luke! Ismael On Tue, Mar 18,