[
https://issues.apache.org/jira/browse/KAFKA-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhruvil Shah updated KAFKA-7076:
--------------------------------
Affects Version/s: 0.11.0.0
0.11.0.1
1.0.0
0.11.0.2
1.1.0
1.0.1
Fix Version/s: 2.0.0
Component/s: core
> Broker startup could be inefficient when using old message format
> -----------------------------------------------------------------
>
> Key: KAFKA-7076
> URL: https://issues.apache.org/jira/browse/KAFKA-7076
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.11.0.0, 0.11.0.1, 1.0.0, 0.11.0.2, 1.1.0, 1.0.1
> Reporter: Dhruvil Shah
> Assignee: Dhruvil Shah
> Priority: Major
> Fix For: 2.0.0
>
>
> During broker startup, we call `Log#recoverSegment` when we find corrupted
> indexes, for segments beyond the last check-pointed recovery point, and for
> any ".swap" segments created by log cleaner. One of the things
> `Log#recoverSegments` does is to build up the producer state, starting from
> any previous snapshot file that is available. For logs using message formats
> older than V2, we could skip building up this producer state which would
> essentially speed up recovery.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
