[
https://issues.apache.org/jira/browse/KAFKA-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005133#comment-17005133
]
ASF GitHub Bot commented on KAFKA-8534:
---------------------------------------
Evelyn-Bayes commented on pull request #7875: KAFKA-8534 - Fix retention size
behaviour
URL: https://github.com/apache/kafka/pull/7875
*More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.*
*Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.*
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> retention.bytes does not work as documented
> -------------------------------------------
>
> Key: KAFKA-8534
> URL: https://issues.apache.org/jira/browse/KAFKA-8534
> Project: Kafka
> Issue Type: Bug
> Components: log
> Affects Versions: 0.11.0.3, 1.0.2, 1.1.1, 2.0.1, 2.1.1, 2.2.1
> Reporter: Evelyn Bayes
> Priority: Major
>
> A log segment isn't deleted when a partition reaches retention.bytes.
> Instead a log segment is deleted when a partition reaches retention.bytes +
> segment.bytes
> This conflicts with the defenition of retention.bytes:
> *_This configuration controls the maximum size a partition (which consists of
> log segments) 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. Since this limit is enforced at the partition
> level, multiply it by the number of partitions to compute the topic retention
> in bytes._*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
