[
https://issues.apache.org/jira/browse/KAFKA-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698541#comment-13698541
]
Jay Kreps commented on KAFKA-918:
---------------------------------
This make sense, should be a pretty easy fix. We would definitely take a patch
against trunk if could still support the older property as a fallback for
compatibility.
> Change log.retention.hours to be log.retention.mins
> ---------------------------------------------------
>
> Key: KAFKA-918
> URL: https://issues.apache.org/jira/browse/KAFKA-918
> Project: Kafka
> Issue Type: New Feature
> Components: config
> Affects Versions: 0.7.2
> Reporter: Jason Weiss
> Labels: features
>
> We stood up a cluster that is processing over 350,000 events per second, with
> each event a fixed payload size of 2K. The storage required to process that
> much data over an hour is beyond what we wanted to pay for at AWS.
> Additionally, we don't have a requirement to keep the files around for an
> extended period after processing.
> It would be tremendously valuable for us to be able to define the
> log.retention in minutes, not hours. For example, we would prefer to only
> keep 30 minutes of logs around.
--
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
