[Bug] docker compose down关闭之后无法启动，必须手动移除tsfile

使用 2.0.8 版本的 Docker Compose 部署复现该故障，然后检查 UnsealedTsFileRecoverPerformer 周围的启动恢复逻辑，以及 iotdb/data/datanode/data 下受影响的文件。比较关闭和重启日志，尤其关注 .tsfile 缺少其 .resource 文件的情况。当服务在正常关闭后无需手动移动文件即可成功重启，并且在确定相关测试区域后为复现的情况补充了覆盖时，即视为完成。

Search before asking

• I searched in the issues and found nothing similar.

Version

版本2.0.8，docker部署

Describe the bug and provide the minimal reproduce step

docker compose关闭服务，再启动时直接报错：
Aborting due to java.lang.OutOfMemoryError: Java heap space # # A fatal error has been detected by the Java Runtime Environment: # # Internal Error (debug.cpp:362), pid=7, tid=468 # fatal error: OutOfMemory encountered: Java heap space # # JRE version: OpenJDK Runtime Environment Temurin-17.0.15+6 (17.0.15+6) (build 17.0.15+6) # Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.15+6 (17.0.15+6, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64) # Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %d" (or dumping to /iotdb/sbin/core.7) # # An error report file with more information is saved as: # /iotdb/sbin/hs_err_pid7.log 2026-07-14 08:51:04,653 [pool-39-IoTDB-TsFile-Recover-2] INFO o.a.i.d.s.d.w.r.f.UnsealedTsFileRecoverPerformer:291 - The compression ratio of tsfile /iotdb/data/datanode/data/sequence/iot_data/8/2949/1784016833721-8-0-0.tsfile is 0.00, totalMemTableSize: 0, the file size: 3867189

解决方案：按gpt提示，通过以下命令找到缺少resource的tsfile:

find ./iotdb/data/datanode/data -type f -name '*.tsfile' |
while IFS= read -r file; do
  [ -f "${file}.resource" ] || echo "$file"
done | tee /tmp/tsfiles-without-resource.txt

wc -l /tmp/tsfiles-without-resource.txt

然后将这几个文件移动走，才能正常启动服务。

What did you expect to see?

服务关闭之后能够自行正常启动，这是一个基本能力。

What did you see instead?

服务实现优雅关闭

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!