Re: In case of Max topic size is reached

segment.bytes This configuration controls the segment file size for the log. Retention and cleaning is always done a file at a time so a larger segment size means fewer files but

Re: UNKNOWN_PRODUCER_ID error when running Streams WordCount demo with processing.guarantee set to EXACTLY_ONCE

unsubscribe On Sat, Jul 21, 2018 at 1:26 AM Guozhang Wang wrote: > Hello Shaobo, > > The situation you observed is a valid case: when a streams application has > very low traffic (like the quickstart example, where you manually type one > message at a time), then it is possible that consumer

Re: In case of Max topic size is reached

And when is that message segment closed? I mean what is the criteria to close the message segment? Can I change that criteria with configuration? On Tue, 1 Jun 2021 at 11:36 PM, Ran Lupovich wrote: > They work simultaneously, topic with cleanup policy of DELETE , will > clean old message

Re: In case of Max topic size is reached

They work simultaneously, topic with cleanup policy of DELETE , will clean old message older than the retention period and also deletes the oldest messages when retention bytes limit is breached, notice this limit is for each partition in a topic and not total size of the topic, notice as well

In case of Max topic size is reached

Hi, Suppose: Maximum Topic size is set to 1 GB Retention hours: 168 What happens in case topic size reaches the maximum size before 168 hours. Will it delete few messages before its expiry though they are eligible to stay for 168 hrs? Regards, Sunil.

MirrorMaker only mirrors a subset of configured topics

Dear all, I’m stuck in getting a setup to work where MirrorMaker consumes from a Confluent Kafka ensemble and produces to Azure Event Hub. The MirrorMaker is started as a service like /etc/systemd/system/kafka-azure-event-hub-mm.service [Unit] Description=Kafka Azure-Event-Hub MM Service