[jira] [Created] (KAFKA-14337) bugs kafka 3.3.1 create topic after delete topic

thanhnd96 created KAFKA-14337: - Summary: bugs kafka 3.3.1 create topic after delete topic Key: KAFKA-14337 URL: https://issues.apache.org/jira/browse/KAFKA-14337 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-14023) MirrorCheckpointTask.syncGroupOffset does not have to check if translated offset from upstream is smaller than the current consumer offset

[ https://issues.apache.org/jira/browse/KAFKA-14023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-14023. - Resolution: Won't Do > MirrorCheckpointTask.syncGroupOffset does not have to check if

Re: [DISCUSS] KIP-874: TopicRoundRobinAssignor

Thanks for clarifying Mathieu, I hadn't seen your PR yet and assumed from your earlier comments that this was still a WIP. I do tend to agree with David on this though, I was also struggling to understand the use case/motivation and felt it was quite specific. As I think David said in his PR

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

Hi, David, Thanks for the explanation. Sounds good to me. Jun On Tue, Oct 25, 2022 at 12:19 PM David Jacot wrote: > Hi Jun, > > That’s right. I propose to tackle this in a separate KIP because the > downgrade need some thinking. > > I would like to point out that the current group coordinator

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

Hey Sophie, Thanks for the KIP. I think this could be useful for a lot of cases. I also think that this could cause a lot of confusion. Just to make sure we are doing our best to prevent people from misusing this feature, I wanted to clarify a couple of things. 1) There will be only an interface

Re: [VOTE] KIP-869: Improve Streams State Restoration Visibility

+1 non binding Thanks for the kip! On Thu, Oct 20, 2022 at 10:25 PM John Roesler wrote: > Thanks for the KIP, Guozhang! > > I'm +1 (binding) > > -John > > On Wed, Oct 12, 2022, at 16:36, Nick Telford wrote: > > Can't wait! > > +1 (non-binding) > > > > On Wed, 12 Oct 2022, 18:02 Guozhang Wang,

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

Hi Jun, That’s right. I propose to tackle this in a separate KIP because the downgrade need some thinking. I would like to point out that the current group coordinator does not support downgrades either so we don’t make it worst. I am personally in favor of doing this KIP before we release the

Re: [DISCUSS] KIP-858: Handle JBOD broker disk failure in KRaft

Hello, There’s now a proposal to address ZK to KRaft migration — KIP-866 — but currently it doesn't address JBOD so I've decided to update this proposal to address that migration scenario. So given that: - When migrating from a ZK cluster running JBOD to KRaft, brokers registering in KRaft

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

Hi, David, Thanks for the reply. The KIP mentioned downgrade support in a future KIP. So, with this KIP, once the new records have been generated on the coordinator, there is no path to downgrade the broker, is that correct? Thanks, Jun On Tue, Oct 25, 2022 at 7:10 AM David Jacot wrote: >

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

Hi Sophie, Thanks for the KIP! I think this is a worthwhile feature to add. I have two main questions about how this new feature will work. 1. You mention that for stateless applications auto-scaling is a sticker situation. But I was thinking that the auto-scaling would actually benefit

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

See Changes: -- [...truncated 508556 lines...] [2022-10-25T15:45:20.556Z] [2022-10-25T15:45:20.556Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 165

Re: Request permissions to contribute to kafka

Hi Jie, You should be good to go now. Cheers, Chris On Tue, Oct 25, 2022 at 11:04 AM Wang Jie wrote: > Hi team, > > I would like to request contributor access to the project. > > Jira-ID: jackwangcs > Wiki-ID: jackwangcs > > Best, > Jie >

Request permissions to contribute to kafka

Hi team, I would like to request contributor access to the project. Jira-ID: jackwangcs Wiki-ID: jackwangcs Best, Jie

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

Hi all, The vote has been open for a while. I plan to close it on Friday if there are no further comments in the discussion thread. Best, David On Wed, Oct 19, 2022 at 6:10 PM Jun Rao wrote: > > Hi, David, > > Thanks for the KIP. +1 > > Jun > > On Wed, Oct 19, 2022 at 2:21 AM Magnus Edenhill

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

Hi Jun, 90.1 You're right. That's a miss on my side. 90.2 That makes sense. Relying on ConsumerGroupTargetAssignmentMetadataValue.AssignmentEpoch should be enough here. 91. When a client side assignor is used, the assignment is computed asynchronously. While it is computed for the group at epoch

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

Hi Magnus, Thanks for your interesting perspective. Your points are totally valid so I will revert this change to the previous version. I have also added the reasoning in the rejected alternative. Best, David On Mon, Oct 24, 2022 at 4:49 PM Magnus Edenhill wrote: > > Hi, one minor comment on

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

See

[jira] [Resolved] (KAFKA-14331) Upgrade to Scala 2.13.10

[ https://issues.apache.org/jira/browse/KAFKA-14331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi-Vass resolved KAFKA-14331. - Resolution: Duplicate > Upgrade to Scala 2.13.10 > > >

Re: [DISCUSS] KIP-874: TopicRoundRobinAssignor

Hi Mathieu, Thanks for the effort that you have put in creating this KIP. I just read it again and I am still confused by the use cases and the motivation. I suppose that this works for your data model but it does not seem to be a general pattern. Overall, I stick to the comment that I made in