You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/08 08:32:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16158301#comment-16158301 ]
ASF GitHub Bot commented on KAFKA-4504:
---------------------------------------
GitHub user omkreddy opened a pull request:
https://github.com/apache/kafka/pull/3814
KAFKA-4504: update retention.bytes config description
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/omkreddy/kafka KAFKA-4504
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3814.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3814
----
commit 02d248f59dccc17f454a62711ef2040293eaba98
Author: Manikumar Reddy <ma...@gmail.com>
Date: 2017-09-08T08:22:59Z
KAFKA-4504: update retention.bytes config description
----
> 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 Manchester
>
> 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.4.14#64029)