[jira] [Updated] (KAFKA-6175) AbstractIndex should cache index file to avoid unnecessary disk access during resize()

["Dong Lin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dong Lin updated KAFKA-6175:
----------------------------
    Fix Version/s: 1.0.1

> AbstractIndex should cache index file to avoid unnecessary disk access during resize()
> --------------------------------------------------------------------------------------
>
>                 Key: KAFKA-6175
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6175
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Dong Lin
>            Assignee: Dong Lin
>             Fix For: 1.0.1
>
>
> Currently when we shutdown a broker, we will call AbstractIndex.resize() for all segments on the broker, regardless of whether the log segment is active or not. AbstractIndex.resize() incurs raf.setLength(), which is expensive because it accesses disks. If we do a threaddump during either LogManger.shutdown() or LogManager.loadLogs(), most threads are in RUNNABLE state at java.io.RandomAccessFile.setLength().
> This patch intends to speed up broker startup and shutdown time by skipping AbstractIndex.resize() for inactive log segments.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)