RE: Kafka consumer group crashing and not able to consume once service is up

Hi Philip, Are you expecting logs from subscriber from our service please do let me know. Thanks, Santhosh Aditya From: Marigowda, Santhosh Aditya Sent: Friday, February 9, 2024 11:32 AM To: Philip Nee ; Jain, Ankit Cc: dev@kafka.apache.org; Namboodiri, Vishnu ; Mudlapur, Rajesh ; Reddy,

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

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.5 #105

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.7 #92

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.6 #143

See

Re: [DISCUSS] KIP-877: Mechanism for plugins and connectors to register metrics

Hi Mickael, Thanks for the KIP, this looks like a great change! 1. I see that one of my concerns was already discussed, and appears to have been concluded with: > I considered Chris' idea of automatically removing metrics but decided to > leave that responsibility to the plugins. After

Re: [VOTE] KIP-390: Support Compression Level (rebooted)

Hi Mickael, +1 to getting KIP-390 merged with the per-codec level config. Thanks, Tom On Fri, 9 Feb 2024 at 07:27, Diop, Assane wrote: > > Hi Mickael > I will take some time today to add some documentation to KIP-984. I actually > have a working implementation of the plugin and I have been

Re: [DISCUSS] KIP-877: Mechanism for plugins and connectors to register metrics

Still need to digest the KIP, but one thing coming to mind: Instead of requiring existing interfaces to implement `Closable`, would it make sense to make `Monitorable extends Closable` to sidestep this issue? -Matthias On 1/25/24 9:03 AM, Mickael Maison wrote: Hi Luke, The reason vary for

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

See Changes: -- [...truncated 369202 lines...] [2024-02-08T19:07:59.972Z] at org.gradle.internal.dispatch.AsyncDispatch.access$000(AsyncDispatch.java:36)

RE: [VOTE] KIP-390: Support Compression Level (rebooted)

Hi Mickael I will take some time today to add some documentation to KIP-984. I actually have a working implementation of the plugin and I have been running test. I would be ready to do a PR anytime. As far as motivation, Divij did asked about that and I responded in an email to the mailing

Re: Kafka consumer group crashing and not able to consume once service is up

Hi, I believe what you sent was the broker log not the client log - client log would be useful to debug the issue. Also, the configuration you provided seems to be your application log - there are a few configuration I'm not sure what they actually mean, e.g. delay, timeout. P On Wed, Feb 7,

Re: Kafka-Streams-Scala for Scala 3

Josep, thanks for helping with this. I was also thinking if we might need a KIP for this change. Since you had the same though, I would say, yes, let's do a KIP. @Matthias: can you prepare a KIP? You can read up on the details on the wiki page:

[jira] [Resolved] (KAFKA-16236) Interactive Query v2 does not support Global KTables

[ https://issues.apache.org/jira/browse/KAFKA-16236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-16236. - Resolution: Duplicate Thanks for filing this tickets. It's duplicate of

Re: Kafka-Streams-Scala for Scala 3

Hey Josep et al, I've created a ticket regarding this. https://issues.apache.org/jira/browse/KAFKA-16237 All the best, Matthias Am Do., 8. Feb. 2024 um 11:42 Uhr schrieb Josep Prat : > > Go ahead and ask for a JIRA and Wiki account (Confluence). Let us know when > your accounts are created and

[jira] [Created] (KAFKA-16237) Kafka-Streams-Scala for Scala 3

Matthias Berndt created KAFKA-16237: --- Summary: Kafka-Streams-Scala for Scala 3 Key: KAFKA-16237 URL: https://issues.apache.org/jira/browse/KAFKA-16237 Project: Kafka Issue Type: New

Re: [DISCUSS] KIP-971 Expose replication-offset-lag MirrorMaker2 metric

Hi, Thanks for the updates. I'm wondering whether we really need the ttl eviction mechanism. The motivation is to "avoid storing stale LRO entries which can cause an eventual OOM error". How could it contain stake entries? I would expect its cache to only contain entries for partitions assigned

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

See Changes: -- [...truncated 348491 lines...] [2024-02-08T12:49:23.221Z] Gradle Test Run :core:test > Gradle Test Executor 96 > KafkaZkClientTest >

Re: [VOTE] KIP-390: Support Compression Level (rebooted)

Sounds good. I am onboard to start with first steps and eventually move towards a place where compression codec settings are more generic / pluggable. -- Divij Vaidya On Wed, Feb 7, 2024 at 3:40 PM Mickael Maison wrote: > Hi Divij, > > Thanks for bringing that point. After reading KIP-984, I

Modifying certain dynamic configurations on the standalone KRaft controller

Hello, I would like to clarify a statement I found in the KRaft documentation, in the "missing features" section [1]: > Modifying certain dynamic configurations on the standalone > KRaft controller Could someone expand on which "certain dynamic configurations" can't be modified in the current

Re: Kafka-Streams-Scala for Scala 3

Go ahead and ask for a JIRA and Wiki account (Confluence). Let us know when your accounts are created and we'll properly set them up so you can create and assign tickets to you. Best, On Thu, Feb 8, 2024 at 11:32 AM Matthias Berndt wrote: > Thanks Josep, I've applied for a JIRA account and

[jira] [Resolved] (KAFKA-12937) Mirrormaker2 can only start from the beginning of a topic

[ https://issues.apache.org/jira/browse/KAFKA-12937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-12937. Resolution: Duplicate > Mirrormaker2 can only start from the beginning of a topic >

Re: Kafka-Streams-Scala for Scala 3

Thanks Josep, I've applied for a JIRA account and addressed your review comments. Am Do., 8. Feb. 2024 um 09:19 Uhr schrieb Josep Prat : > > Hi Matthias, > > I think for this particular case it would be worth creating a JIRA ticket > for this as it's a new "feature". > Regarding the change

[jira] [Resolved] (KAFKA-8259) Build RPM for Kafka

[ https://issues.apache.org/jira/browse/KAFKA-8259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-8259. --- Resolution: Won't Do > Build RPM for Kafka > --- > > Key:

[jira] [Resolved] (KAFKA-9094) Validate the replicas for partition reassignments triggered through the /admin/reassign_partitions zNode

[ https://issues.apache.org/jira/browse/KAFKA-9094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-9094. --- Resolution: Won't Do > Validate the replicas for partition reassignments triggered through

Re: Kafka-Streams-Scala for Scala 3

Hi Matthias, I think for this particular case it would be worth creating a JIRA ticket for this as it's a new "feature". Regarding the change itself, I think we need to clarify how the release process would work. Right now, the script `gradlewAll` is used (which basically runs the build with

[jira] [Created] (KAFKA-16236) Interactive Query v2 does not support Global KTables

Christian Zügner created KAFKA-16236: Summary: Interactive Query v2 does not support Global KTables Key: KAFKA-16236 URL: https://issues.apache.org/jira/browse/KAFKA-16236 Project: Kafka