You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Justin (JIRA)" <ji...@apache.org> on 2016/12/07 15:38:58 UTC
[jira] [Updated] (KAFKA-4504) Details of retention.bytes property
at Topic level are not clear on how they impact partition size
[ https://issues.apache.org/jira/browse/KAFKA-4504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin updated KAFKA-4504:
--------------------------
Description:
Problem:
Details of retention.bytes property at Topic level are not clear on how they impact partition size
Business Impact:
Users are setting retention.bytes and not seeing the desired store amount of data.
Current Text:
This configuration controls the maximum size a log can grow to before we will discard old log segments to free up space if we are using the "delete" retention policy. By default there is no size limit only a time limit.
Proposed change:
This configuration controls the maximum size a log can grow to before we will discard old log segments to free up space if we are using the "delete" retention policy. By default there is no size limit only a time limit. Please note, this is calculated as retention.bytes * number of partitions on the given topic for the total amount of disk space to be used.
was:
Problem:
Details of retention.bytes property at Topic level are not clear on how they impact the system
Business Impact:
Proposed fix:
Summary: Details of retention.bytes property at Topic level are not clear on how they impact partition size (was: Details of retention.bytes property at Topic level are not clear on how they impact on system)
> Details of retention.bytes property at Topic level are not clear on how they impact partition size
> --------------------------------------------------------------------------------------------------
>
> Key: KAFKA-4504
> URL: https://issues.apache.org/jira/browse/KAFKA-4504
> Project: Kafka
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 0.10.0.1
> Reporter: Justin
>
> Problem:
> Details of retention.bytes property at Topic level are not clear on how they impact partition size
> Business Impact:
> Users are setting retention.bytes and not seeing the desired store amount of data.
> Current Text:
> This configuration controls the maximum size a log can grow to before we will discard old log segments to free up space if we are using the "delete" retention policy. By default there is no size limit only a time limit.
> Proposed change:
> This configuration controls the maximum size a log can grow to before we will discard old log segments to free up space if we are using the "delete" retention policy. By default there is no size limit only a time limit. Please note, this is calculated as retention.bytes * number of partitions on the given topic for the total amount of disk space to be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)