kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-3802) log mtimes reset on broker restart
Date Wed, 06 Jul 2016 15:15:11 GMT

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

Ismael Juma updated KAFKA-3802:
-------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> log mtimes reset on broker restart
> ----------------------------------
>
>                 Key: KAFKA-3802
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3802
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 0.9.0.1
>            Reporter: Andrew Otto
>             Fix For: 0.10.0.1
>
>
> Folks over in http://mail-archives.apache.org/mod_mbox/kafka-users/201605.mbox/%3CCAO8=cz0RAGJAd1Acx4GEqcWJ+RKd1gMdAvkjWytwthKSzfgb5Q@mail.gmail.com%3E
are commenting about this issue.
> In 0.9, any data log file that was on
> disk before the broker has it's mtime modified to the time of the broker
> restart.
> This causes problems with log retention, as all the files then look like
> they contain recent data to kafka.  We use the default log retention of 7
> days, but if all the files are touched at the same time, this can cause us
> to retain up to 2 weeks of log data, which can fill up our disks.
> This happens *most* of the time, but seemingly not all.  We have seen broker restarts
where mtimes were not changed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message