Re: Apache Kafka 3.6.0 release

Thanks Satish. This is done  Justine On Mon, Sep 4, 2023 at 5:16 PM Satish Duggana wrote: > Hey Justine, > I went through KAFKA-15424 and the PR[1]. It seems there are no > dependent changes missing in 3.6 branch. They seem to be low risk as > you mentioned. Please merge it to the 3.6 branch

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

See

Re: Apache Kafka 3.6.0 release

Hey Justine, I went through KAFKA-15424 and the PR[1]. It seems there are no dependent changes missing in 3.6 branch. They seem to be low risk as you mentioned. Please merge it to the 3.6 branch as well. 1. https://github.com/apache/kafka/pull/14324. Thanks, Satish. On Tue, 5 Sept 2023 at

Re: Apache Kafka 3.6.0 release

Sorry I meant to add the jira as well. https://issues.apache.org/jira/browse/KAFKA-15424 Justine On Mon, Sep 4, 2023 at 4:34 PM Justine Olshan wrote: > Hey Satish, > > I was working on adding dynamic configuration for > transaction verification. The PR is approved and ready to merge into

Re: Apache Kafka 3.6.0 release

Hey Satish, I was working on adding dynamic configuration for transaction verification. The PR is approved and ready to merge into trunk. I was thinking I could also add it to 3.6 since it is fairly low risk. What do you think? Justine On Sat, Sep 2, 2023 at 6:21 PM Sophie Blee-Goldman wrote:

Unable to start the Kafka with Kraft in Windows 11

Hi *Team*, I am following the steps mentioned here https://kafka.apache.org/quickstart to Install the Kafka. *Windows* 11 *Kafka Version* https://www.apache.org/dyn/closer.cgi?path=/kafka/3.5.0/kafka_2.13-3.5.0.tgz *64 Bit Operating System* *Step1: Generate the Cluster UUID*

[jira] [Resolved] (KAFKA-14936) Add Grace Period To Stream Table Join

[ https://issues.apache.org/jira/browse/KAFKA-14936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Walker Carlson resolved KAFKA-14936. Resolution: Done > Add Grace Period To Stream Table Join >

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

See

[jira] [Created] (KAFKA-15431) Add support to assert offloaded segment for already produced event in Tiered Storage Framework

Kamal Chandraprakash created KAFKA-15431: Summary: Add support to assert offloaded segment for already produced event in Tiered Storage Framework Key: KAFKA-15431 URL:

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.6 #19

See

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

See

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

My approach is to create another thread to regularly request and update the end offset of each partition for the `keySet` in the collection `lastReplicatedSourceOffsets` mentioned by your kip (if there is no update for a long time, it will be removed from `lastReplicatedSourceOffsets`).

[jira] [Resolved] (KAFKA-15052) Fix flaky test QuorumControllerTest.testBalancePartitionLeaders()

[ https://issues.apache.org/jira/browse/KAFKA-15052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-15052. --- Resolution: Fixed > Fix flaky test QuorumControllerTest.testBalancePartitionLeaders() >

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

@huqedi replying to your comment on the PR ( https://github.com/apache/kafka/pull/14077#discussion_r1314592488), quote: "I guess we have a disagreement about lag? My understanding of lag is: the real LEO of the source cluster partition minus the LEO that has been written to the target cluster. It

[jira] [Created] (KAFKA-15430) Kafla create replca partition on controller node

Andrii Vysotskiy created KAFKA-15430: Summary: Kafla create replca partition on controller node Key: KAFKA-15430 URL: https://issues.apache.org/jira/browse/KAFKA-15430 Project: Kafka

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

I already have the PR for this so if it will make it easier to discuss, feel free to take a look: https://github.com/apache/kafka/pull/14077 On Mon, 4 Sept 2023 at 09:17, hudeqi <16120...@bjtu.edu.cn> wrote: > But does the offset of the last `ConsumerRecord` obtained in poll not only > represent

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

The offset lag is the difference between the last end offset of the source partition (LEO) and the last replicated source offset (LRO). The offset of the last `ConsumerRecord` for a partition obtained in poll represent the LEO in the source cluster, and LRO is obtained at producer callback where

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

But does the offset of the last `ConsumerRecord` obtained in poll not only represent the offset of this record in the source cluster? It seems that it cannot represent the LEO of the source cluster for this partition. I understand that the offset lag introduced here should be the LEO of the

Re: KIP-976: Cluster-wide dynamic log adjustment for Kafka Connect

Hi Chris, thanks. This looks like a useful feature. Due to the idempotent nature of PUT, I guess that the last_modified timestamp won't change if the same request is repeated successively. Should we add a unit test for that? On Mon, Sep 4, 2023 at 6:17 AM Ashwin wrote: > > Hi Chris, > > Thanks

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

Hi huqedi, I've considered two solutions: 1) https://kafka.apache.org/24/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html#endOffsets-java.util.Collection- This option requires an additional network call, so not preferable 2) Manually getting the last element of List in the response of

Re: KIP-976: Cluster-wide dynamic log adjustment for Kafka Connect

> If no modifications to a logging namespace have > been made, won't the namespace itself be omitted > from the response? It looks like we currently only > return loggers that have non-null log levels in the *> **GET /admin/loggers* endpoint. This can be ignored - I didn't account for the fact

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.6 #18

See

Re: KIP-976: Cluster-wide dynamic log adjustment for Kafka Connect

Hi Chris, Thanks for the KIP, this looks like a really useful addition to Kafka Connect's log level REST APIs! I have a few questions and comments: > If no modifications to the namespace have > been made since the worker was started, > they will be null If no modifications to a logging

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

See