Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-179

Log files always touched when broker is bounced

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Implemented
    • Affects Version/s: None
    • Fix Version/s: 0.8.2.0
    • Component/s: core
    • Labels:

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              raulcf Raul Castro Fernandez
              Reporter:
              jjkoshy Joel Koshy
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: