[
https://issues.apache.org/jira/browse/KAFKA-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029711#comment-14029711
]
Raul Castro Fernandez commented on KAFKA-179:
---------------------------------------------
Just tried it. It seems that it is already fixed. After creating a couple of
topics and reinitialising the brokers a couple of times, the mtime of the log
and index files does not change.
> Log files always touched when broker is bounced
> -----------------------------------------------
>
> Key: KAFKA-179
> URL: https://issues.apache.org/jira/browse/KAFKA-179
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Joel Koshy
> Priority: Minor
> Labels: newbie
> Fix For: 0.8.2
>
>
> It looks like the latest log segment is always touched when the broker upon
> start-up regardless of whether it has corrupt data or not, which fudges the
> segment's mtime. Minor issue, but I found it a bit misleading when trying to
> verify a log cleanup setting in production. I think it should be as simple as
> adding a guard in FileMessageSet's recover method to skip truncate if
> validUpTo == the length of the segment. Will test this later.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
