Re: [DISCUSS] KIP-1201: Add disk threshold strategy to prevent disk full failure

Hi peng, Thanks for the suggestion, In fact, we already have an implementation of auto deletion on Kafka and it has been running in our environment for more than 1 year. The implementation add four broker config: - `disk.used.threshold.enable`: Whether to enable disk usage threshold for auto cl

Re: [DISCUSS] KIP-997: update WindowRangeQuery and unify WindowKeyQuery and WindowRangeQuery

Hi all, Gentle Reminder on this. I would appreciate feedback from the community on KIP-997. Any thoughts on the potential benefits and trade-offs of adding key range query support, as well as any suggestions for how to address the issue of non-lexicographically sorted keys. Thanks, ~ Rajani On T

Re: [VOTE] 4.0.1 RC0

Hi Christo, Could you take a look at this issue, and see if we want to include this patch into v4.0.1? https://lists.apache.org/thread/83kqzk823xcxfj5w2t68sdftmo7t0bpz Thank you. Luke On Fri, Aug 1, 2025 at 2:03 AM Matthias J. Sax wrote: > Hey Christo, > > can you take a look at https://github

Re: [VOTE] 4.1.0 RC1

Hi Mickael, Could you take a look at this issue, and see if we want to include this patch into v4.1.0? https://lists.apache.org/thread/83kqzk823xcxfj5w2t68sdftmo7t0bpz Thank you. Luke On Sat, Aug 2, 2025 at 1:50 AM Jun Rao wrote: > I chatted with Andrew Schofield. So, share is not required in

Re: [VOTE] KIP-1172: Improve EndToEndLatency tool

Hi everyone, Thanks for the feedback and votes. The KIP-1172 has been approved with 3 binding votes (Andrew, TengYao and Chia-Ping) and 2 non-binding votes (Krik and Federico). Regards, Nick On Mon, Aug 4, 2025 at 9:51 AM Junwang Guo wrote: > Hi Chia-Ping, > > Thanks for the suggestion, I've

Re: [VOTE] KIP-1172: Improve EndToEndLatency tool

Hi Chia-Ping, Thanks for the suggestion, I've updated the jira tile. Regards, Nick On Sun, Aug 3, 2025 at 6:23 PM Chia-Ping Tsai wrote: > +1 (binding) > > For the other one, could you help revise the title? I did not name the > JIRA very well, but it'd be nice to align it with previous KIP dis

Kafka Consumer Not Receiving Messages Until Restart

Dear Apache Kafka Development Team, I hope you're doing well. I'm encountering an issue with our Kafka setup where the consumer stops receiving messages after running for a period of time, even though: - The Kafka producer continues to send payloads successfully - The consumer rema

Re: [VOTE] KIP-1160: Enable returning supported features from a specific broker

+1 (binding) On 2025/06/25 06:18:32 PoAn Yang wrote: > Hi all, > > I would like to start a vote on KIP-1160. Thank you. > > KIP: https://cwiki.apache.org/confluence/x/5gnXF > > Discussion thread: > https://lists.apache.org/thread/mbjlgbv2q4x5ml7mx93ls77bg93wtrfy > > Regards, > PoAn

Re: [DISCUSS] KIP-1160: Enable returning supported features from a specific broker

yes, that sounds good to me PoAn Yang 於 2025年8月3日 週日 下午7:23寫道： > Hi Chia-Ping, > > chia_02: Yes, it’s better to return TimeoutException if the node > is not available. However, for FeatureCommand, we can follow > ReassignPartitionsCommand to return AdminCommandFailedException. > WDYT? > > > http

Re: [DISCUSS] KIP-1160: Enable returning supported features from a specific broker

Hi Chia-Ping, chia_02: Yes, it’s better to return TimeoutException if the node is not available. However, for FeatureCommand, we can follow ReassignPartitionsCommand to return AdminCommandFailedException. WDYT? https://github.com/apache/kafka/blob/ea771563e0b5f047027ab1ffa67d976d8df26864/tools/sr

Re: [VOTE] KIP-1172: Improve EndToEndLatency tool

+1 (binding) For the other one, could you help revise the title? I did not name the JIRA very well, but it'd be nice to align it with previous KIP discussion. Best, Chia-Ping On 2025/07/09 13:04:51 Junwang Guo wrote: > Hi all, > > I would like to start a vote on KIP-1172: Improve EndToEndLaten

Re: [DISCUSS] KIP-1160: Enable returning supported features from a specific broker

chia_02: If the node is nonexistent, the API throws BrokerIdNotRegisteredException. I added related test cases to test plan. Throwing BrokerIdNotRegisteredException seems a bit odd to me, since the broker may be temporarily unavailable. Perhaps, it should throw a `TimeoutException`, similar to `i