You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jiangjie Qin (JIRA)" <ji...@apache.org> on 2017/02/04 03:21:52 UTC
[jira] [Assigned] (KAFKA-4734) timeindex on old segments not
trimmed to actual size
[ https://issues.apache.org/jira/browse/KAFKA-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jiangjie Qin reassigned KAFKA-4734:
-----------------------------------
Assignee: Jiangjie Qin
> timeindex on old segments not trimmed to actual size
> -----------------------------------------------------
>
> Key: KAFKA-4734
> URL: https://issues.apache.org/jira/browse/KAFKA-4734
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.10.1.0
> Reporter: Jun Rao
> Assignee: Jiangjie Qin
>
> When upgrading from 0.9.0 to 0.10.1, the broker creates empty .timeindex files on old log segments without trimming them. So, on disk, you will see .timeindex files with preallocated size.
> -rw-r--r-- 1 junrao wheel 10485756 Feb 3 15:15 00000000000000000000.timeindex
> -rw-r--r-- 1 junrao wheel 10485756 Feb 3 15:15 00000000000000000960.timeindex
> -rw-r--r-- 1 junrao wheel 10485756 Feb 3 15:15 00000000000000001920.timeindex
> -rw-r--r-- 1 junrao wheel 10485756 Feb 3 15:15 00000000000000002880.timeindex
> -rw-r--r-- 1 junrao wheel 10485756 Feb 3 15:15 00000000000000003840.timeindex
> -rw-r--r-- 1 junrao wheel 10485760 Feb 3 15:15 00000000000000004800.index
> -rw-r--r-- 1 junrao wheel 10485756 Feb 3 15:15 00000000000000004800.timeindex
> If the broker is restarted again, all .timeindex files (except for the one on the active segment) are trimmed to 0 size. It would be better if we do that in the first place.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)