kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Serduik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-1112) broker can not start itself after kafka is killed with -9
Date Fri, 01 Nov 2013 17:23:19 GMT

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

Denis Serduik commented on KAFKA-1112:

We've also faced with such behavior. Moreover, it doesn't fail right after startup, it start
listening for requests(at least open the port) before checking  the index and syncing internal
state. Thus it kind of difficult to figure out from startup script whether Kafka actually
started without adding some ugly sleeps.

> 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
> 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

View raw message