kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Olson (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-1379) Partition reassignment resets clock for time-based retention
Date Fri, 11 Aug 2017 21:21:01 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Olson resolved KAFKA-1379.
---------------------------------
       Resolution: Fixed
         Assignee: Jiangjie Qin
    Fix Version/s: 0.10.1.0

Marking this bug as resolved in 0.10.1.0 based on the statement "The log retention time is
no longer based on last modified time of the log segments. Instead it will be based on the
largest timestamp of the messages in a log segment." in http://kafka.apache.org/documentation.html#upgrade_10_1_breaking

> 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
>            Assignee: Jiangjie Qin
>             Fix For: 0.10.1.0
>
>
> 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.4.14#64029)

Mime
View raw message