Skip to content

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

Open

Description

@YiuTerran

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!

Activity

  1. HTHou commented on Jul 15, 2026

    @HTHou
    Contributor

    这个问题需要看看为何重启时会出现OOM,正常情况不会出现这个问题。

  2. HTHou commented on Jul 15, 2026

    @HTHou
    Contributor

    一个可能的想法是不是重启后减少了内存配置,导致内存大小不足以支持WAL恢复所需要的内存了?

  3. YiuTerran commented on Jul 16, 2026

    @YiuTerran
    Author

    @HTHou 之后又遇到类似问题,还是启动立刻OOM。然后我加了内存也没用,本来是8G,我加到12G,还是起不起来。GPT说可能是恢复的并发数太高导致OOM了,我尝试限制容器CPU核数为1,还是不行。真是没辙了,只能删文件。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions