[
https://issues.apache.org/jira/browse/IOTDB-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17780886#comment-17780886
]
Haonan Hou commented on IOTDB-6221:
-----------------------------------
https://github.com/apache/iotdb/pull/11276
> Bad tsfile being recoverd from wal
> ----------------------------------
>
> Key: IOTDB-6221
> URL: https://issues.apache.org/jira/browse/IOTDB-6221
> Project: Apache IoTDB
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: Haonan Hou
> Priority: Major
>
> After OS system shutdown and restart IoTDB service, there is a broken TsFile
> cannot be compacted.
> It caused by this 0-level TsFile contains two chunk groups with same device
> id. And there are several issues to fix.
> # Before restart IoTDB, this TsFile ended with a lot of zero bytes. However
> the current selfcheck logic will treated these zero bytes as correct chunk
> group, which cause the truncate position is not correct.
> # In TsFilePlanRedoer, there is a wrong logic of filter the InsertPlan from
> wal. Some InsertPlans which should be filtered are inserted into the
> recovering memtable. Therefore, the TsFile will contains two chunk groups
> with same device id.
> # in UnsealedTsFileRecoverPerformer, there is an outdated redundant logic
> should be removed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
