[jira] [Resolved] (KAFKA-18669) Connector is restarted before it is started

[ https://issues.apache.org/jira/browse/KAFKA-18669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anil Dasari resolved KAFKA-18669. - Resolution: Done > Connector is restarted before it is started > ---

Re: [VOTE] 4.0.0 RC0

Given that this is effectively a documentation fix, a cherry-pick makes sense. Ismael On Fri, Feb 28, 2025 at 1:30 PM Jun Rao wrote: > Hi, David, > > We just fixed https://issues.apache.org/jira/browse/KAFKA-18864. Not sure > if you want to cherry-pick it to 4.0. > > Thanks, > > Jun > > On Thu,

Re: [DISCUSS] KIP-1124: Providing a clear Kafka Client upgrade path

Thanks for pointing me to test Ismael. Glad to see I just missed it, and that we indeed have a test for it. Feel free to edit the KIP directly – I'm totally fine with it. Thanks a lot! Thanks Kuan-Po! I did update the wiki page and added more details. I did follow Bruno's suggestion, to be

Re: [VOTE] 4.0.0 RC0

Hi, David, We just fixed https://issues.apache.org/jira/browse/KAFKA-18864. Not sure if you want to cherry-pick it to 4.0. Thanks, Jun On Thu, Feb 27, 2025 at 7:22 PM Ismael Juma wrote: > Thanks for the testing Kirk. Can you please file an issue for the repeated > log to make sure it doesn't

[jira] [Resolved] (KAFKA-18864) remove the Evolving tag from stable public interfaces

[ https://issues.apache.org/jira/browse/KAFKA-18864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-18864. - Fix Version/s: 4.1.0 Resolution: Fixed > remove the Evolving tag from stable public interfaces >

Re: Metadata requests for subset of partitions

> > It's certainly been a topic that's come up before. In certain situations > > the current approach is a bit heavy-handed. The current approach for > > fetching metadata has a number of benefits: it keeps the protocol from > > being too chatty, which reduces load on the brokers and makes maintain

APACHE KAFKA DOCUMENTATION

I hope this email finds you well. I am currently researching the Apache Kafka documentation and would like to confirm whether it is generated using *ASP pages* or a different documentation framework. Could you please clarify the format and tools used in creating and maintaining the official Kafka

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

See

Re: [DISCUSS] KIP-1124: Providing a clear Kafka Client upgrade path

hi Matthias thanks for your updates. it looks great and readable. Regarding API compatibility, we state "we only provide API backward compatibility for version 3.7, 3.8, and 3.9" However, within Connect APIs, we have removed a public API that was deprecated by 3.7 [0][1]. Since this KIP will

Re: Metadata requests for subset of partitions

On Thu, Feb 27, 2025 at 5:39 PM Kirk True wrote: > Hi Michał, > > On Thu, Feb 27, 2025, at 3:44 AM, Michał Łowicki wrote: > > Hi there! > > > > Is there any reason why Metadata requests > > do not > > support fetching metadata for sub

Re: Metadata requests for subset of partitions

On Fri, Feb 28, 2025 at 2:14 PM Stanislav Kozlovski < stanislavkozlov...@apache.org> wrote: > Thanks for the concrete data. > > In essence, 199,000 partition metadata entries (MetadataResponsePartition) > are unnecessarily sent over the network in this example. > > Looking at the response object[0

Re: [DISCUSS] KIP-1124: Providing a clear Kafka Client upgrade path

Hi Matthias, Two quick comments: 1. Yes, please help edit the KIP directly. It's easy enough to revert if Kuan disagrees. 2. Regarding client upgrades, the test in https://github.com/apache/kafka/pull/18193/files is an example of test that only starts from 2.1 (since we did not merge #18193). Is

Re: [DISCUSS] KIP-1124: Providing a clear Kafka Client upgrade path

Hi Matthias, Feel free to edit the KIP directly – I'm totally fine with it. Thanks a lot! Best, Kuan-Po Tseng On 2025/02/28 07:35:10 "Matthias J. Sax" wrote: > Thanks all. I am happy that we are making progress to close this out. > > As mentioned in my (long) email last Friday, I also think tha

[jira] [Created] (KAFKA-18904) Listing of configs for dynamically created resources is mysterious

Andrew Schofield created KAFKA-18904: Summary: Listing of configs for dynamically created resources is mysterious Key: KAFKA-18904 URL: https://issues.apache.org/jira/browse/KAFKA-18904 Project: K

Kafka Producer Configuration Optimization for Production

We are preparing to deploy our *Java API-based Kafka Producer* to production and want to ensure our configuration is optimized. However, we want to validate the configuration for *high reliability and optimal performance* in production. *Message Load Details* - *Message Rate:* 3,000 to 5,000

[jira] [Resolved] (KAFKA-18734) Implement share partition metrics for share fetch

[ https://issues.apache.org/jira/browse/KAFKA-18734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-18734. --- Resolution: Fixed > Implement share partition metrics for share fetch >

[jira] [Created] (KAFKA-18903) Use curl + jq in update-cache.sh

David Arthur created KAFKA-18903: Summary: Use curl + jq in update-cache.sh Key: KAFKA-18903 URL: https://issues.apache.org/jira/browse/KAFKA-18903 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-18657) Flaky SharePartitionManagerTest

[ https://issues.apache.org/jira/browse/KAFKA-18657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18657. -- Fix Version/s: 4.1.0 Resolution: Fixed > Flaky SharePartitionManagerTest >

[jira] [Resolved] (KAFKA-18522) Limit fetch records batches as per acquired records

[ https://issues.apache.org/jira/browse/KAFKA-18522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-18522. --- Fix Version/s: 4.1.0 Resolution: Fixed The first PR is merged and for MemoryRecords w

[jira] [Created] (KAFKA-18901) Improve redistribution of share group SimpleAssignor

Andrew Schofield created KAFKA-18901: Summary: Improve redistribution of share group SimpleAssignor Key: KAFKA-18901 URL: https://issues.apache.org/jira/browse/KAFKA-18901 Project: Kafka

[jira] [Created] (KAFKA-18902) Experiment with ShareConsumer option to throw on poll if there are unacked records

Andrew Schofield created KAFKA-18902: Summary: Experiment with ShareConsumer option to throw on poll if there are unacked records Key: KAFKA-18902 URL: https://issues.apache.org/jira/browse/KAFKA-18902

[jira] [Created] (KAFKA-18900) Create a consumer config to select between implicit and explicit acknowledgement

Andrew Schofield created KAFKA-18900: Summary: Create a consumer config to select between implicit and explicit acknowledgement Key: KAFKA-18900 URL: https://issues.apache.org/jira/browse/KAFKA-18900

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

Andrew Schofield created KAFKA-18899: Summary: Limit retry time for ShareConsumer.commitAsync Key: KAFKA-18899 URL: https://issues.apache.org/jira/browse/KAFKA-18899 Project: Kafka Issue

Re: [VOTE] 4.0.0 RC0

Thanks for the testing Kirk. Can you please file an issue for the repeated log to make sure it doesn't get lost in this thread? Ismael On Thu, Feb 27, 2025 at 2:54 PM Kirk True wrote: > Hi David, > > I focused on testing the clients using Java 11: > > My steps: > > 1. Start the broker via the n

Re: Metadata requests for subset of partitions

Thanks for the concrete data. In essence, 199,000 partition metadata entries (MetadataResponsePartition) are unnecessarily sent over the network in this example. Looking at the response object[0], I count about 50 bytes per entry. That's a total of 9.95MB of extra information going over the wir

Re: Metadata requests for subset of partitions

On Fri, Feb 28, 2025 at 10:10 AM Stanislav Kozlovski < stanislavkozlov...@apache.org> wrote: > > > It's certainly been a topic that's come up before. In certain > situations > > > the current approach is a bit heavy-handed. The current approach for > > > fetching metadata has a number of benefits: