[
https://issues.apache.org/jira/browse/KAFKA-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511208#comment-13511208
]
Swapnil Ghike edited comment on KAFKA-235 at 12/6/12 7:59 AM:
--------------------------------------------------------------
Yes, KAFKA-475 added a feature to 0.7 and 0.8 that rolls a new log segment
based on the age of the old segment. So in essence, a new log segment is rolled
when the old segment exceeds its max permissible size or max permissible age.
These maximum size and age limits can be configured in KafkaConfig.
was (Author: swapnilghike):
Yes, KAFKA-475 added a feature to 0.7 and 0.8 that rolls a new log segment
based on the age of the old segment. So in essence, a new log segment is rolled
when the old segment exceeds its max permissible size or max permissible age.
> Add a 'log.file.age' configuration parameter to force rotation of log files
> after they've reached a certain age
> ---------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-235
> URL: https://issues.apache.org/jira/browse/KAFKA-235
> Project: Kafka
> Issue Type: New Feature
> Components: core
> Affects Versions: 0.7
> Reporter: Mathias Herberts
> Assignee: Swapnil Ghike
> Fix For: 0.8, 0.7.2
>
>
> The Kafka client has the ability to start consuming at an offset before or
> after a given point in time. The granularity of this offset is the log file
> as the Kafka servers do not keep track of arrival time of various messages.
> This means that the granularity of offsets relative to time depends on
> arrival rate of messages and thus of log file rotation. A topic with lots of
> messages will have its log files rotated very often (thus each spans a short
> time interval) whereas a topic with very few messages might not see its log
> files rotated for hours.
> In order to circumvent this granularity disparity, having a parameter that
> would force log file rotation after a certain delay (xxx ms) would allow for
> pretty much constant time granularity to be available at the cost of more
> file descriptor being used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
