[
https://issues.apache.org/jira/browse/KAFKA-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805392#comment-13805392
]
Swapnil Ghike commented on KAFKA-918:
-------------------------------------
I think it's confusing to allow both configs in 'if .. else', one could plug in
both configs and would need to open up the logs to see which property is
getting used. Is it because we want to maintain backward 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
> Assignee: Alin Vasile
> Labels: features, newbie
> Fix For: 0.8.1
>
> Attachments: issue_918.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
