kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antony Stubbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-6235) Kafka should have a last resort retention setting for max disk used
Date Sat, 25 Nov 2017 19:15:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Antony Stubbs updated KAFKA-6235:
---------------------------------
    Summary: Kafka should have a last resort retention setting for max disk used  (was: Kafka
should have an emergency retention setting for max disk used)

> Kafka should have a last resort retention setting for max disk used
> -------------------------------------------------------------------
>
>                 Key: KAFKA-6235
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6235
>             Project: Kafka
>          Issue Type: New Feature
>            Reporter: Antony Stubbs
>
> Kafka should have an emergency retention setting for max disk used to prevent the broker
running out of disk and partitions going off line. When this max is reached, Kafka could perhaps
delete segments from the largest topics. Would have to be used with care as current behaviour
is to preserve data at the cost of availability. This would favour availability over data
retention.
> At the moment it's quite hard to reason about disk usage and Kafka as the max byte settings
are all per partition, and the math can get complicated when you have lots of topics of different
use cases and sizes..



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message