fangjinuo created KAFKA-4972:
--------------------------------
Summary: Kafka 0.10.0 Found a corrupted index file during Kafka
broker startup
Key: KAFKA-4972
URL: https://issues.apache.org/jira/browse/KAFKA-4972
Project: Kafka
Issue Type: Bug
Components: log
Affects Versions: 0.10.0.0
Environment: JDK: HotSpot x64 1.7.0_80
Tag: 0.10.0
Reporter: fangjinuo
Priority: Critical
Fix For: 0.11.0.0, 0.12.0.0, 0.10.2.0, 0.10.1.1, 0.10.1.0,
0.10.0.1, 0.10.0.0
Attachments: Snap3.png
After force shutdown all kafka brokers one by one, restart them one by one, but
a broker startup failure.
The following WARN leval log was found in the log file:
found a corrutped index file, xxxx.index , delet it ...
you can view details by following attachment.
I look up some codes in core module, found out :
the nonthreadsafe method LogSegment.append(offset, messages) has tow caller:
1) Log.append(messages) // here has a synchronized
lock
2) LogCleaner.cleanInto(topicAndPartition, source, dest, map, retainDeletes,
messageFormatVersion) // here has not
So I guess this may be the reason for the repeated offset in 00000xx.log file
(logsegment's .log)
Although this is just my inference, but I hope that this problem can be quickly
repaired
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
