You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Sriharsha Chintalapani (JIRA)" <ji...@apache.org> on 2016/02/29 18:16:18 UTC
[jira] [Resolved] (KAFKA-3291) DumpLogSegment tool should also
provide an option to only verify index sanity.
[ https://issues.apache.org/jira/browse/KAFKA-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sriharsha Chintalapani resolved KAFKA-3291.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 0.10.0.0
Issue resolved by pull request 975
[https://github.com/apache/kafka/pull/975]
> DumpLogSegment tool should also provide an option to only verify index sanity.
> ------------------------------------------------------------------------------
>
> Key: KAFKA-3291
> URL: https://issues.apache.org/jira/browse/KAFKA-3291
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Reporter: Parth Brahmbhatt
> Assignee: Parth Brahmbhatt
> Fix For: 0.10.0.0
>
>
> DumpLogSegment tool should call index.sanityCheck function as part of index sanity check as that function determines if an index will be rebuilt on restart or not. This is a cheap check as it only checks the file size and can help in scenarios where customer is trying to figure out which index files will be rebuilt on startup which directly affects the broker bootstrap time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)