kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neha Narkhede (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-1112) broker can not start itself after kafka is killed with -9
Date Tue, 05 Nov 2013 18:45:18 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814110#comment-13814110
] 

Neha Narkhede commented on KAFKA-1112:
--------------------------------------

Stack trace -

[2013-11-01 17:46:02,685] INFO Loading log 'foo-4' (kafka.log.LogManager)
[2013-11-01 17:46:04,898] FATAL Fatal error during KafkaServerStable startup. Prepare to shutdown
(kafka.server.KafkaServerStartable)
java.lang.IllegalArgumentException: requirement failed: Corrupt index found, index file (/mnt/u001/temp/kafka-logs/foo-4/00000000000000000000.index)
has non-zero size but the last offset is 0 and the base offset is 0
at scala.Predef$.require(Predef.scala:145)
at kafka.log.Log$$anonfun$loadSegments$5.apply(Log.scala:161)
at kafka.log.Log$$anonfun$loadSegments$5.apply(Log.scala:160)
at scala.collection.Iterator$class.foreach(Iterator.scala:631)
at scala.collection.JavaConversions$JIteratorWrapper.foreach(JavaConversions.scala:474)
at scala.collection.IterableLike$class.foreach(IterableLike.scala:79)
at scala.collection.JavaConversions$JCollectionWrapper.foreach(JavaCo

> broker can not start itself after kafka is killed with -9
> ---------------------------------------------------------
>
>                 Key: KAFKA-1112
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1112
>             Project: Kafka
>          Issue Type: Bug
>          Components: log
>    Affects Versions: 0.8, 0.8.1
>            Reporter: Kane Kim
>            Assignee: Guozhang Wang
>            Priority: Critical
>
> When I kill kafka with -9, broker cannot start itself because of corrupted index logs.
I think kafka should try to delete/rebuild indexes itself without manual intervention. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message