[
https://issues.apache.org/jira/browse/KAFKA-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107065#comment-14107065
]
Steven Zhen Wu commented on KAFKA-1489:
---------------------------------------
[~jimhoagland] thanks for the clarification. per-direction/volume makes sense.
But it shouldn't take much work to set up. user can just configure the
disk-full-policy properties as Jay mentioned earlier. understand that it is
probably fine for some use cases to do nothing and just drop the new messages.
But drop-msgs-when-disk-full can be very useful to many users assuming
consumers are usually fairly close to write head. then it is usually harmless
to drop old msgs.
> 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/%[email protected]%3E
--
This message was sent by Atlassian JIRA
(v6.2#6252)
