[
https://issues.apache.org/jira/browse/KAFKA-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16268849#comment-16268849
]
Jeffrey Zampieron commented on KAFKA-1489:
------------------------------------------
I'd like to propose thinking about this from a bullet-proof operational
perspective.
When I'm running a cluster, about the only thing I care about is not filling up
the disk and dropping new data... almost everyone wants to use the disk as a
giant circular buffer. Rotating out the old when it gets full, no matter which
topic, partition, whatever.
Regardless of if I have unbalanced topics, partitions, none of that matters
here... it's strictly *per-broker* (containerized or not) that I want to retain
X amount of bytes of data in my data folder in order to stay running.
> Global threshold on data retention size
> ---------------------------------------
>
> Key: KAFKA-1489
> URL: https://issues.apache.org/jira/browse/KAFKA-1489
> Project: Kafka
> Issue Type: New Feature
> Components: log
> Affects Versions: 0.8.1.1
> Reporter: Andras Sereny
>
> Currently, Kafka has per topic settings to control the size of one single log
> (log.retention.bytes). With lots of topics of different volume and as they
> grow in number, it could become tedious to maintain topic level settings
> applying to a single log.
> Often, a chunk of disk space is dedicated to Kafka that hosts all logs
> stored, so it'd make sense to have a configurable threshold to control how
> much space *all* data in one Kafka log data directory can take up.
> See also:
> http://mail-archives.apache.org/mod_mbox/kafka-users/201406.mbox/browser
> http://mail-archives.apache.org/mod_mbox/kafka-users/201311.mbox/%3c20131107015125.gc9...@jkoshy-ld.linkedin.biz%3E
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
