Re: Request to be added in contributors list of Apache Kafka

Did you already create a JIRA account? (It's self-service.) After you have created your account, please share your user name so we can grant you contributor permissions. -Matthias On 10/4/21 8:47 PM, Nandini Nelson wrote: Hello Kafka Community, I would like to contribute to Apache Kafka an

Re: kafka streams commit.interval.ms for at-least-once too high

The main motivation for a shorter commit interval for EOS is end-to-end-latency. A Topology could consist of multiple sub-topologies and the end-to-end-latency for the EOS case is roughly commit-interval times number-of-subtopologies. For regular rebalances/restarts, a longer commit interval h

Request to be added in contributors list of Apache Kafka

Hello Kafka Community, I would like to contribute to Apache Kafka and want to pick up some issues. I read here that I need to be added to the contributors list in order to start working on a jira. Request you to a

Replica fetcher not fetching post rolling reboots

Hello, We are seeing an issue on rolling restarts where replicas of a few partitions are lagging and never catchup. The log files for these partitions look the same size on all the brokers- including the ones where the replicas are lagging. The failedpartitionscount metric is still at 0 but the

Re: mm2: size of target vs source topic

My guess is that MM2 decompressed, batched, then compressed the data again in bigger chunks - in case the batches in the source were small, MM2 could be able to improve the compression with bigger batches. 2021.10.04. 19:21 keltezéssel, Men Lim írta: bump On Wed, Sep 29, 2021 at 4:09 PM Men L

Re: mm2: size of target vs source topic

bump On Wed, Sep 29, 2021 at 4:09 PM Men Lim wrote: > Hi all, > I'm setting up two new clusters today and using mm2 to replicate data from > clusterA --> clusterB. I noticed that the topic has the same amount of > record but the size is small by 5x. > > source topic is 6.975 MB > target topic i

kafka streams commit.interval.ms for at-least-once too high

Hi All, I am looking into the commit.interval.ms in kafka streams which says that it is the time interval at which streams would commit offsets to source topics. However for exactly-once guarantee, default of this time is 100ms whereas for at-least-once it is 3ms (i.e. 30sec) Why is there such