[
https://issues.apache.org/jira/browse/KAFKA-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps updated KAFKA-1112:
-----------------------------
Attachment: KAFKA-1112-v2.patch
Added a new patch that addresses issues raised.
Jun
1. I don't think this is true. The check is for exact match.
2. Removed.
3. Done
Neha
1. I think I am handling this--in the case of zero we don't do a full scan.
2. Ack, fixed.
3. Well the sanity check is POST recovery. So if we have a corrupt index after
recovery we have a bug, I don't think we should automatically try to recovery
from this (that would be another recovery).
4. done
5. Yeah, haven't had time yet.
> 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: Jay Kreps
> Priority: Critical
> Attachments: KAFKA-1112-v1.patch, KAFKA-1112-v2.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.1#6144)
