Re: [DISCUSS] (continued) KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi Jun, Thanks for your thorough review. There is already a vote thread if you want to vote. Best, David On Tue, Oct 18, 2022 at 11:07 PM Jun Rao wrote: > > Hi, David, > > Thanks for the reply. No more comments from me. > > 80. Yes, since PrepareAssignment returns topicIds, using topicId in > C

Re: [VOTE] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Great work on the KIP, David. +1 (nonbinding) Den fre 14 okt. 2022 kl 11:50 skrev Luke Chen : > Hi David, > > I made a final pass and LGTM now. > +1 from me. > > Luke > > On Wed, Oct 5, 2022 at 12:32 AM Guozhang Wang wrote: > > > Hello David, > > > > I've made my final pass on the doc and I thi

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #1310

See Changes: -- [...truncated 340076 lines...] [Pipeline] dir [2022-10-19T09:41:49.717Z] Running in /home/jenkins/workspace/Kafka_kafka_trunk/streams/quickstart/test-strea

[jira] [Created] (KAFKA-14322) Kafka node eating Disk continuously

Abhijit Patil created KAFKA-14322: - Summary: Kafka node eating Disk continuously Key: KAFKA-14322 URL: https://issues.apache.org/jira/browse/KAFKA-14322 Project: Kafka Issue Type: Bug

Re: [DISCUSS] (continued) KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi all, I would like to highlight a small change that I did in the KIP around static membership based on Magnus' feedback. Magnus pointed out that two members using the same static instance id will basically continuously fence each other. The issue is that the existing member is fenced and replace

Re: [DISCUSS] KIP-878: Autoscaling for Statically Partitioned Streams

Sophie, Thank you for the KIP! Choosing the number of partitions in a Streams app is a tricky task because of how difficult it is to re-partition; I'm glad you're working on an improvement. I've got two questions: First, `StaticStreamsPartitioner` is an interface that we (Streams users) must impl

Re: [VOTE] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi, David, Thanks for the KIP. +1 Jun On Wed, Oct 19, 2022 at 2:21 AM Magnus Edenhill wrote: > Great work on the KIP, David. > > +1 (nonbinding) > > Den fre 14 okt. 2022 kl 11:50 skrev Luke Chen : > > > Hi David, > > > > I made a final pass and LGTM now. > > +1 from me. > > > > Luke > > > > On

Re: [DISCUSS] (continued) KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi David, A few questions below: 1. In regard to this comment: > Every member is uniquely identified by a UUID. This is called the Member ID. This UUID is generated on the server side and given to the member when it joins the group. It is used in all the communication with the group coordinator

Re: [DISCUSS] (continued) KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi Jason, Thanks for your comments. 1. My intent was to let the consumer reuse its member id when it rejoins the group after being fenced. I basically wanted to differentiate a restart of the consumer from a rejoin of the member on the server side. Joining with a member id would only be allowed w

[jira] [Created] (KAFKA-14323) KRaft broker time based snapshots

José Armando García Sancio created KAFKA-14323: -- Summary: KRaft broker time based snapshots Key: KAFKA-14323 URL: https://issues.apache.org/jira/browse/KAFKA-14323 Project: Kafka

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #1311

See

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.3 #108

See Changes: -- [...truncated 499177 lines...] [2022-10-19T19:54:56.601Z] org.apache.kafka.streams.processor.internals.HandlingSourceTopicDeletionIntegrationTest > shouldThr

Re: [DISCUSS] KIP-878: Autoscaling for Statically Partitioned Streams

Thanks for your questions, I would say that your understanding sounds correct based on what you described but I'll try to add some clarity. The basic idea is that, as you said, any keys that are processed before time T will go to partition 1. All of those keys should then continue to be routed to p

[jira] [Created] (KAFKA-14324) [CVE-2018-25032] introduced by rocksdbjni:6.29.4.1

VZhang created KAFKA-14324: -- Summary: [CVE-2018-25032] introduced by rocksdbjni:6.29.4.1 Key: KAFKA-14324 URL: https://issues.apache.org/jira/browse/KAFKA-14324 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-14252) Create background thread skeleton

[ https://issues.apache.org/jira/browse/KAFKA-14252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Nee resolved KAFKA-14252. Resolution: Fixed > Create background thread skeleton > - > >

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #1312

See