[
https://issues.apache.org/jira/browse/KAFKA-10889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17255527#comment-17255527
]
Jiangjie Qin commented on KAFKA-10889:
--------------------------------------
It looks that the broker is working as design. I am not sure what would be
expected behavior here. If a message of timestamp T was appended to the log,
and the retention is set to R, that message will only be deleted after T + R.
Because Kafka maintains the contiguity of the messages, all the messages after
that message won't be deleted before that message expires.
One potential improvement might be disallowing messages whose timestamp is
greater than the current system time by too much. But that may also hurt some
other use cases. And defining "too much" could also be tricky.
> The log cleaner is not working for topic partitions
> ---------------------------------------------------
>
> Key: KAFKA-10889
> URL: https://issues.apache.org/jira/browse/KAFKA-10889
> Project: Kafka
> Issue Type: Bug
> Components: log cleaner
> Affects Versions: 2.0.0
> Reporter: Wenbing Shen
> Assignee: Wenbing Shen
> Priority: Blocker
> Attachments: 0880c08b0110fcdd9b0c.png, 0880c08b0110fcddfb0b.png,
> image-2020-12-28-17-17-15-947.png
>
>
> * I have a topic that is reserved for the default of 7 days, but the log
> exists from October 26th to December 25th today.The log cleaner doesn't seem
> to be working on it.This seems to be an underlying problem in Kafka.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
