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

Posted to notifications@iotdb.apache.org by "Jialin Qiao (Jira)" <ji...@apache.org> on 2022/05/12 01:19:00 UTC

[jira] [Assigned] (IOTDB-3160) TsFile will be corrupted when flushing memtable appears OOM.

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

Jialin Qiao reassigned IOTDB-3160:
----------------------------------

    Assignee: Haiming Zhu

> TsFile will be corrupted when flushing memtable appears OOM. 
> -------------------------------------------------------------
>
>                 Key: IOTDB-3160
>                 URL: https://issues.apache.org/jira/browse/IOTDB-3160
>             Project: Apache IoTDB
>          Issue Type: Bug
>    Affects Versions: master branch, 0.13.0
>            Reporter: 周沛辰
>            Assignee: Haiming Zhu
>            Priority: Major
>         Attachments: image-2022-05-11-16-59-49-557.png, image-2022-05-11-17-08-56-755.png
>
>
> When flushing memtable appears OOM, the file will be corrupted with metadata only and cannot be repaired at the next restart. The result may be  as following: 
> When an exception is caught in the flushing memtable, the following logic will be executed to call the TsFileIOWriter's endfile, causing the file to have only the metadata area but no data area. After the next restart, memTable is considered to have flushed properly and WAL is not used to restore tsfile.
> !image-2022-05-11-16-59-49-557.png!
> !image-2022-05-11-17-08-56-755.png|width=1594,height=592!



--
This message was sent by Atlassian Jira
(v8.20.7#820007)