You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Andrew Olson (JIRA)" <ji...@apache.org> on 2017/02/13 18:43:41 UTC
[jira] [Comment Edited] (KAFKA-1379) Partition reassignment resets
clock for time-based retention
[ https://issues.apache.org/jira/browse/KAFKA-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864128#comment-15864128 ]
Andrew Olson edited comment on KAFKA-1379 at 2/13/17 6:43 PM:
--------------------------------------------------------------
[~hachikuji] Jason, could you confirm if this bug has been fixed? According to http://kafka.apache.org/documentation.html#upgrade_10_1_breaking it appears so.
was (Author: noslowerdna):
[~hachikuji] Jason, could you confirm if this bug has been fixed?
> 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
> Components: log
> 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.15#6346)