[
https://issues.apache.org/jira/browse/KAFKA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057656#comment-14057656
]
Manikumar Reddy commented on KAFKA-1480:
----------------------------------------
We have introduced "log.roll.ms" server property as part of
https://issues.apache.org/jira/browse/KAFKA-1325.
This should solve this JIRA.
We already have topic-level-configs retention.ms, segment.ms at milli-second
granularity.
> support log.roll.minutes
> ------------------------
>
> Key: KAFKA-1480
> URL: https://issues.apache.org/jira/browse/KAFKA-1480
> Project: Kafka
> Issue Type: Improvement
> Components: config
> Reporter: Steven Zhen Wu
> Assignee: Manikumar Reddy
>
> Steven,
> We initially set the rolling criterion based on hours to avoid too frequent
> log rolling and in turn too small segment files. For your case this may be
> reasonable to set the rolling criterion on minutes. Could you file a JIRA?
> Guozhang
> On Mon, Jun 2, 2014 at 4:00 PM, Steven Wu <steve...@netflix.com.invalid>
> wrote:
> > This might be a bit unusual. We have a topic that we only need to keep last
> > 5 minutes of msgs so that replay from beginning is fast.
> >
> > Although retention.ms has time unit of minute, segment.ms ONLY has time
> > unit of hour. If I understand cleanup correctly, it can only delete files
> > that are rolled over. If true, the minimal retention period can be actually
> > one hour.
> >
> > is there any particular reason for different time units for retention and
> > roll? Can we add "log.roll.minutes"?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
