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

2025-05-03 Thread Apache Jenkins Server
See

[jira] [Created] (KAFKA-19236) Auto.offset.reset "by-duration" should reset a single time

2025-05-03 Thread Matthias J. Sax (Jira)
Matthias J. Sax created KAFKA-19236: --- Summary: Auto.offset.reset "by-duration" should reset a single time Key: KAFKA-19236 URL: https://issues.apache.org/jira/browse/KAFKA-19236 Project: Kafka

Re: [DISCUSS] KIP-1153: Extending support for Microsecond Precision for Kafka Connect

2025-05-03 Thread pritam kumar
Hi Chris, Can you please review this one too? On Sat, Apr 5, 2025 at 7:00 AM pritam kumar wrote: > Hi Kafka Community, > Sorry due to some changes I had to change the link to the kip. > Here is the updated KIP link: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1154%3A+Extending+suppor

Re: [DISCUSS] KIP-1173: Connect Storage Topics Sharing Across Clusters

2025-05-03 Thread pritam kumar
Hi chris, thank you very much for the review and the feedback, 1. On read amplification part, the bulk read where the whole topic is read will happen on when the cluster is restarted and apart from that it will only be reading the additional records that also by discarding the records of other clus

Re: [DISCUSS] KIP-1173: Connect Storage Topics Sharing Across Clusters

2025-05-03 Thread Chris Egerton
Hi Pritam, I think Greg's concerns about read amplification are still unaddressed, no? I'd guess that the config topic is unlikely to experience an increase in load large enough to cause problems, but what about the status topic (especially if there's, e.g. a K8s operator constantly restarting fai

Re: [DISCUSS] KIP-1173: Connect Storage Topics Sharing Across Clusters

2025-05-03 Thread pritam kumar
Hi Greg, Thank you for your review, and apologies for the delayed response—I was out of office. *"Broker resource utilization is expected to decrease by approximately 20%, primarily due to reduced partition count and metadata overhead."* To clarify, this estimate compares two scenarios: 1. Clusters

Re: [DISCUSS] KIP-1105: Make remote log manager thread-pool configs dynamic

2025-05-03 Thread Chia-Ping Tsai
hi Kamal Thanks for the response. I will file a jira and KIP for it. Best, Chia-Ping > Kamal Chandraprakash 於 2025年5月3日 晚上10:54 寫道: > > 1. Yes, it was considered during the implementation of KIP-950 but the > config was not proposed in the KIP and > the KIP/Feature freeze date was passed by t

Re: [DISCUSS] KIP-1105: Make remote log manager thread-pool configs dynamic

2025-05-03 Thread Kamal Chandraprakash
1. Yes, it was considered during the implementation of KIP-950 but the config was not proposed in the KIP and the KIP/Feature freeze date was passed by that time. 2. Having the RLMFollowerTask thread dynamically configurable is a useful feature. I'm +1 on adding the config to maintain consistency

Re: [DISCUSS] KIP-1161: cleanup.policy shouldn't be empty

2025-05-03 Thread 黃竣陽
Hi Jun, chia, Thanks for all the comments. They have all been addressed in the updated KIP. Best Regards, Jiunn-Yang > Chia-Ping Tsai 於 2025年5月3日 凌晨2:03 寫道: > > hi Jiunn-Yang > > in the "Compatibility, Deprecation, and Migration Plan", could you add > description to remind readers that "clean

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

2025-05-03 Thread Chia-Ping Tsai (Jira)
[ https://issues.apache.org/jira/browse/KAFKA-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18267. Resolution: Fixed > Add test for CloseOption > > >

[DISCUSS] KIP-1139: Add support for OAuth jwt-bearer grant type

2025-05-03 Thread Emanuele Sabellico
Thanks for the KIP Kirk! I have this question: 1. `sasl.oauthbearer.assertion.algorithm` is used to select the JOSE signature algorithm so it also contains the hash size. Just you have to choose one that matches your private key algorithm, only SHA256 at the moment. What kind of error is returned

Re: [DISCUSS] KIP-1105: Make remote log manager thread-pool configs dynamic

2025-05-03 Thread Chia-Ping Tsai
hi Kamal Thanks for your response. I have two minor questions. 1. Have we considered adding a new config for RLMFolloweTask, such as remote.log.manager.follower.thread.pool.size, for consistency? 2. Additionally, with the specific config, the size of RLMFolloweTask can be dynamically configure