[GitHub] [iotdb] qiaojialin opened a new issue #2607: Current system mode is read-only

[GitBox <gi...@apache.org>]

qiaojialin opened a new issue #2607:
URL: https://github.com/apache/iotdb/issues/2607


   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
   - OOM
   
   If OOM,  you could config manually or upgrade to version 0.11.3 or a later version.
   
   How to config OOM: in  iotdb-engine.properties
   
   enable_parameter_adapter=false
   tsfile_size_threshold=100000000
   memtable_size_threshold=JVM memory/2/storage group number/4


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [iotdb] wangchao316 commented on issue #2607: Current system mode is read-only

[GitBox <gi...@apache.org>]

wangchao316 commented on issue #2607:
URL: https://github.com/apache/iotdb/issues/2607#issuecomment-774843680


   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.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org