kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rajini Sivaram (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-4972) Kafka 0.10.0 Found a corrupted index file during Kafka broker startup
Date Thu, 09 Nov 2017 10:53:00 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rajini Sivaram updated KAFKA-4972:
----------------------------------
    Fix Version/s:     (was: 0.11.0.2)

Moving this out to the next release since there is no PR yet to include in 0.11.0.2. Let me
know if anyone can provide a PR in time for 0.11.0.2.

> 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
(v6.4.14#64029)

Mime
View raw message