[ https://issues.apache.org/jira/browse/KAFKA-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168160#comment-15168160 ]
ASF GitHub Bot commented on KAFKA-3291: --------------------------------------- GitHub user Parth-Brahmbhatt opened a pull request: https://github.com/apache/kafka/pull/975 KAFKA-3291: DumpLogSegment tool should also provide an option to only… … verify index sanity. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Parth-Brahmbhatt/kafka KAFKA-3291 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/975.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #975 ---- commit fdc52b7edf1d9a9f73cf7b42ee4c30382e8471eb Author: Parth Brahmbhatt <brahmbhatt.pa...@gmail.com> Date: 2016-02-26T00:14:34Z KAFKA-3291: DumpLogSegment tool should also provide an option to only verify index sanity. ---- > 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 > > 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)