[IOTDB-3160] TsFile will be corrupted when flushing memtable appears OOM.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: master branch, 0.13.0
• Fix Version/s: 0.14.0, 0.13.1
• Labels: pull-request-available
• Sprint: 2022-5-StorageEngine
• Assignee: Haiming Zhu
• Reporter: 周沛辰
• Created: 11/May/22 09:09
• Updated: 27/Sep/22 07:20
• Resolved: 16/May/22 14:01

Description

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.

Issue Links

• is related to: IOTDB-4512 Flush OOM cause corrupt TsFile
• links to: GitHub Pull Request #5892
• links to: GitHub Pull Request #5926