[
https://issues.apache.org/jira/browse/KAFKA-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333338#comment-14333338
]
Moritz Siuts commented on KAFKA-1379:
-------------------------------------
This also happens when a broker dies and loses it's data.
When the broker comes back without any data it will use more and more disk
space until it doubles the used disk space until the retention kicks in and the
usage drops to normal.
IMHO this is pretty bad for disaster scenarios, so I would like to see a higher
prio on this.
> Partition reassignment resets clock for time-based retention
> ------------------------------------------------------------
>
> Key: KAFKA-1379
> URL: https://issues.apache.org/jira/browse/KAFKA-1379
> Project: Kafka
> Issue Type: Bug
> Reporter: Joel Koshy
>
> Since retention is driven off mod-times reassigned partitions will result in
> data that has been on a leader to be retained for another full retention
> cycle. E.g., if retention is seven days and you reassign partitions on the
> sixth day then those partitions will remain on the replicas for another
> seven days.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
