Current system mode is read-only
- Dominant language
- Java
- Stars
- 6.4k
- Forks
- 1.2k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 115
Description
This means meeting error when flushing data to disk.
You could search "change system mode to read-only" in the error log to see what happened.
Some common reasons:
- Disk space is full
- Too many open files
- OOM
If OOM, two ways:
(1) config manually if you use 0.10 or earlier version:
conf/iotdb-engine.properties:
enable_parameter_adapter=false
tsfile_size_threshold=100000000
memtable_size_threshold=JVM memory/2/storage group number/4
(2) upgrade to version 0.11.2 or a later version
Generally, in 0.11 version, you do not need to config manually. If still OOM, you could still try to config
conf/iotdb-engine.properties:
enable_mem_control=false
tsfile_size_threshold=100000000
memtable_size_threshold=JVM memory/2/storage group number/4
If still OOM, lower the memtable_size_threshold!
If still, contact us... Wechat:tietouqiao
Contributor guide
Research direction
Start with the error-log entry containing "change system mode to read-only" and inspect conf/iotdb-engine.properties for the listed memory and flush settings. Compare the referenced IoTDB versions and verify a reproducible resolution for the read-only mode; the issue names no source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100