Current system mode is read-only

[qiaojialin]

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

[wangchao316]

hi jialin, I discuss this question in this issue.
https://issues.apache.org/jira/browse/IOTDB-1136

we could add recover mechanism for only-read mode...
Generally, the recovery mechanism is applicable to most failure scenarios. In extreme failure scenarios (such as full disk), the recovery interval can be used to determine whether the failure is a common failure or an extreme failure.