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
Fix For: 0.8
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
