You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jay Kreps (JIRA)" <ji...@apache.org> on 2012/12/06 06:16:58 UTC
[jira] [Assigned] (KAFKA-235) Add a 'log.file.age' configuration
parameter to force rotation of log files after they've reached a certain
age
[ https://issues.apache.org/jira/browse/KAFKA-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jay Kreps reassigned KAFKA-235:
-------------------------------
Assignee: Swapnil Ghike
Didn't we do this?
> 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
>
> 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