Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Date: Thu, 16 Jun 2016 04:35:05 +0000 (UTC)
From: "Manikumar Reddy (JIRA)" <jira@apache.org>
To: dev@kafka.apache.org
Message-ID: <JIRA.12976594.1465328830000.977.1466051705230@Atlassian.JIRA>
In-Reply-To: <JIRA.12976594.1465328830000@Atlassian.JIRA>
References: <JIRA.12976594.1465328830000@Atlassian.JIRA> <JIRA.12976594.1465328830991@arcas>
Subject: [jira] [Updated] (KAFKA-3802) log mtimes reset on broker restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 16 Jun 2016 04:35:07 -0000


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

Manikumar Reddy updated KAFKA-3802:
-----------------------------------
    Status: Patch Available  (was: Open)

> 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)