[ https://issues.apache.org/jira/browse/KAFKA-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109350#comment-14109350 ]
Gwen Shapira commented on KAFKA-1489: ------------------------------------- I actually like the idea of configuring max bytes rather than %. People love configuring 10% free space, but then modern servers often have 36TB space and 10% is a lot of space to waste! I also like the idea of dropping the oldest segment for each log on the space-crunched machine. Its straight forward to explain and implement, and segment sizes are configurable per topic and globally, so admins have ample control. > 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 > Assignee: Jay Kreps > Labels: newbie > > 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.2#6252)
