[ https://issues.apache.org/jira/browse/KAFKA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063604#comment-14063604 ]
Jun Rao commented on KAFKA-1112: -------------------------------- This seems to happen on a clean restart (the following log entry indicates there is no log recovery). So, this could be a different issue. Could you open a separate jira? 2014-07-11T00:53:17+00:00 i-6b948138 local3.info 2014-07-11 - 00:53:17,961 INFO main kafka.log.LogManager.info - Found clean shutdown file. Skipping recovery for all logs in data directory '/mnt/kafka_logs' > 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, 0.8.1 > Reporter: Kane Kim > Assignee: Jay Kreps > Priority: Critical > Fix For: 0.8.1 > > Attachments: KAFKA-1112-v1.patch, KAFKA-1112-v2.patch, > KAFKA-1112-v3.patch, KAFKA-1112-v4.patch, KAFKA-1112.out > > > 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.2#6252)