You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@iotdb.apache.org by "Haonan Hou (Jira)" <ji...@apache.org> on 2021/08/04 08:38:00 UTC

[jira] [Assigned] (IOTDB-1546) OOM when upgrading large 0.11 TsFile to 0.12

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

Haonan Hou reassigned IOTDB-1546:
---------------------------------

    Assignee: Haonan Hou

> OOM when upgrading large 0.11 TsFile to 0.12
> --------------------------------------------
>
>                 Key: IOTDB-1546
>                 URL: https://issues.apache.org/jira/browse/IOTDB-1546
>             Project: Apache IoTDB
>          Issue Type: Bug
>    Affects Versions: master branch, 0.12.2-SNAPSHOT
>            Reporter: Haonan Hou
>            Assignee: Haonan Hou
>            Priority: Major
>
> Some users meet OOM when upgrading some large-size merged 0.11 TsFiles.
> The reasons is that the merged TsFile may contains some very large ChunkGroups. However the current upgrading logic is upgrading ChunkGroup by ChunkGroup, which means the upgrade tool will load the whole ChunkGroup into memory. 
> The idea to fix it is altering the logic to upgrading Chunk by Chunk. By this way, we don't need to load the whole ChunkGroup into memory and can reduce the memory usage significantly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)