[
https://issues.apache.org/jira/browse/KAFKA-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335027#comment-16335027
]
Ewen Cheslack-Postava commented on KAFKA-4972:
----------------------------------------------
[~ijuma] anything to do here or are we at a loss until we have more info? I'd
like to bump out of this release (and maybe just remove fixVersion entirely if
we don't even know what the issue is).
> 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
> Labels: reliability
> Fix For: 1.0.1
>
> Attachments: Snap3.png
>
>
> -deleted text-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
(v7.6.3#76005)
