[
https://issues.apache.org/jira/browse/KAFKA-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jay Kreps resolved KAFKA-561.
-----------------------------
Resolution: Fixed
Fix Version/s: 0.8.1
Assignee: Jay Kreps
This was fixed as part of the log refactoring.
> Rebuild index file for a log segment if there is none
> -----------------------------------------------------
>
> Key: KAFKA-561
> URL: https://issues.apache.org/jira/browse/KAFKA-561
> Project: Kafka
> Issue Type: New Feature
> Reporter: Jay Kreps
> Assignee: Jay Kreps
> Fix For: 0.8.1
>
>
> There are two ways an index file could be missing:
> 1. Someone could delete it or it could be lost due to file corruption
> 2. The server could crash in the middle of rolling the log after having
> created the new log segment but before having created the corresponding index
> segment.
> Regardless it would be nice to recover gracefully from this and rebuild the
> index segment off the corresponding log segment if this happened. This will
> be slow.
> This should be done after KAFKA-521.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira