Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.5 #16

See Changes: -- [...truncated 468240 lines...] [2023-06-02T05:03:47.068Z] [2023-06-02T05:03:47.068Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 178 >

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.5 #15

See Changes: -- [...truncated 468828 lines...] [2023-06-02T02:13:49.444Z] [2023-06-02T02:13:49.444Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 182 >

[jira] [Created] (KAFKA-15048) Improve handling of non-fatal quorum controller errors

Colin McCabe created KAFKA-15048: Summary: Improve handling of non-fatal quorum controller errors Key: KAFKA-15048 URL: https://issues.apache.org/jira/browse/KAFKA-15048 Project: Kafka Issue

[DISCUSS] KIP-938: Add more metrics for measuring KRaft performance

Hi all, I posted a KIP to add some more metrics for measuring KRaft performance. Take a look at: https://cwiki.apache.org/confluence/x/gBU0Dw best, Colin

Re: [VOTE] 3.5.0 RC0

Hi Mickael, Can you start the new RC tomorrow? There's one last PR we'd like to get in. If we can't get it in by tomorrow then let's go ahead anyway. Thanks very much, Colin On Thu, Jun 1, 2023, at 14:15, Mickael Maison wrote: > Hi David, > > The PR you mentioned is merged now. Can I start

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.5 #14

See Changes: -- [...truncated 562608 lines...] [2023-06-01T22:04:02.871Z] > Task :connect:api:publishToMavenLocal [2023-06-01T22:04:04.589Z] > Task :streams:javadoc

Re: [DISCUSS] KIP-923: Add A Grace Period to Stream Table Join

Hey Bruno thanks for the feedback. 1) I will add this to the kip, but stream time only advances as the when the buffer receives a new record. 2) You are correct, I will add a failure section on to the kip. Since the records wont change in the buffer from when they are read from the topic they

Re: [VOTE] 3.5.0 RC0

Hi David, The PR you mentioned is merged now. Can I start working on a new RC or is there more work needed? It seems the associated ticket is still open. Thanks, Mickael On Wed, 31 May 2023, 23:52 Justine Olshan, wrote: > Hey Mickael -- > This is done. Thanks! > > On Wed, May 31, 2023 at

Re: [DISCUSS] Regarding Old PRs

This is worthwhile, but can we use a bot for this? Many other projects do so already. Ismael On Thu, Jun 1, 2023 at 9:24 AM Josep Prat wrote: > Hi Kafka devs, > > Seeing that we have over a 1000 PRs and that we want to try to keep the > number low. I was thinking if it would make sense to go

Re: [DISCUSS] Regarding Old PRs

Hey Josep, 2-3weeks is pretty optimistic, but anything over a year can probably be closed. If there's no response. If they don't or we can't get any answer, we could close the > PRs after 2 to 3 weeks. Regular contributors can't label their own PRs though - it requires a committer/collaborator

Re: [DISCUSS] Regarding Old PRs

Hi Josep, Sounds like an important task for the community & project. I would be happy to help in reaching out to the PR authors. Thanks, Kirk > On Jun 1, 2023, at 9:24 AM, Josep Prat wrote: > > Hi Kafka devs, > > Seeing that we have over a 1000 PRs and that we want to try to keep the >

Re: [DISCUSS] KIP-925: rack aware task assignment in Kafka Streams

Hi Colt, Thanks for the feedback. > most deployments have three racks, RF=3, and one replica for each partition in each rack This KIP is mainly targeting the case where the client won't always be in the same rack as any replica. There's some proposal to make RF=2 and use other tiered storage to

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.5 #13

See Changes: -- [...truncated 472017 lines...] [2023-06-01T18:18:26.112Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 184 > RestoreIntegrationTest >

Re: [DISCUSS] KIP-925: rack aware task assignment in Kafka Streams

Hi all, I've got a rather naive question here. The spiritual goal of this KIP is to reduce cross-rack traffic (normally, this manifests itself in terms of a higher AWS/Azure bill as cloud providers charge for cross-AZ traffic). To generalize, most deployments have three racks, RF=3, and one

Re: [DISCUSS] KIP-925: rack aware task assignment in Kafka Streams

Hi Bruno, dropping config rack.aware.assignment.enabled and add value NONE to the enum for the possible values of config rack.aware.assignment.strategy sounds good to me. On Thu, Jun 1, 2023 at 12:39 AM Bruno Cadonna wrote: > Hi Hao, > > Thanks for the updates! > > What do you think about

[DISCUSS] Regarding Old PRs

Hi Kafka devs, Seeing that we have over a 1000 PRs and that we want to try to keep the number low. I was thinking if it would make sense to go through the oldest PRs and ping the authors to see if they want/can to go back to them and finish them. If they don't or we can't get any answer, we could

[GitHub] [kafka-site] mimaison opened a new pull request, #518: MINOR: Update upgrade to 3.5 section

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

[jira] [Resolved] (KAFKA-15017) New ClientQuotas are not written to ZK from snapshot

[ https://issues.apache.org/jira/browse/KAFKA-15017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Proven Provenzano resolved KAFKA-15017. --- Resolution: Fixed > New ClientQuotas are not written to ZK from snapshot >

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.5 #12

See Changes: -- [...truncated 467270 lines...] [2023-06-01T12:36:51.459Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 177 > StoreQueryIntegrationTest >

[jira] [Created] (KAFKA-15047) Handle rolling segments when the active segment's retention is breached incase of tiered storage is enabled.

Satish Duggana created KAFKA-15047: -- Summary: Handle rolling segments when the active segment's retention is breached incase of tiered storage is enabled. Key: KAFKA-15047 URL:

Re: [DISCUSS] KIP-932: Queues for Kafka

Hi Andrew, Thank you for the KIP, exciting work you are doing :) I have 2 questions: 1. I understand that EOS won't be supported for share-groups (yet), but read_committed fetch will still be possible, correct? 2. I have a very broad question about the proposed solution: why not let the

Re: [DISCUSS] KIP-923: Add A Grace Period to Stream Table Join

Hi Walker, thanks for the KIP! Here my feedback: 1. It is still not clear to me when stream time for the buffer advances. What is the event that let the stream time advance? In the discussion, I do not understand what you mean by "The segment store already has an observed stream time, we

Re: [DISCUSS] KIP-852 Optimize calculation of size for log in remote tier

Satish / Jun Do you have any thoughts on this? -- Divij Vaidya On Tue, Feb 14, 2023 at 4:15 PM Divij Vaidya wrote: > Hey Jun > > It has been a while since this KIP got some attention. While we wait for > Satish to chime in here, perhaps I can answer your question. > > > Could you explain

Re: [VOTE] 3.4.1 RC3

Hi all, Thanks to everyone who has tested and voted for the RC3 so far! Currently, I've got 2 binding votes and 3 non-binding votes: Binding +1 PMC votes: * Chris Egerton * Mickael Maison Non-binding votes: * Federico Valeri * Jakub Scholz * Josep Prat If anyone is available (especially PMC

Re: [DISCUSS] KIP-925: rack aware task assignment in Kafka Streams

Hi Hao, Thanks for the updates! What do you think about dropping config rack.aware.assignment.enabled and add value NONE to the enum for the possible values of config rack.aware.assignment.strategy? Best, Bruno On 31.05.23 23:31, Hao Li wrote: Hi all, I've updated the KIP based on the

Re: [DISCUSS] solutions for broker OOM caused by many producer IDs

Hi Omnia, Thanks for putting this together into the KIP! I'll have a look when available. Thanks. Luke On Thu, Jun 1, 2023 at 1:50 AM Justine Olshan wrote: > Hey Omnia, > > I was doing a bit of snooping (I actually just get updates for the KIP > page) and I saw this draft was in progress. I