segment.bytes <https://docs.confluent.io/platform/current/installation/configuration/topic-configs.html#topicconfigs_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 less granular control over retention segment.ms <https://docs.confluent.io/platform/current/installation/configuration/topic-configs.html#topicconfigs_segment.ms> This configuration controls the period of time after which Kafka will force the log to roll even if the segment file isn't full to ensure that retention can delete or compact old data בתאריך יום ד׳, 2 ביוני 2021, 03:14, מאת sunil chaudhari < sunilmchaudhar...@gmail.com>: > 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 <ranlupov...@gmail.com> > wrote: > > > 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 that deletion kicks off only on "closed" message segments > > > > בתאריך יום ג׳, 1 ביוני 2021, 20:57, מאת sunil chaudhari < > > sunilmchaudhar...@gmail.com>: > > > > > 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. > > > > > >
