[
https://issues.apache.org/jira/browse/IOTDB-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274197#comment-17274197
]
Xiangdong Huang commented on IOTDB-1136:
----------------------------------------
> 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.
It is ok for the recovery discussion. I come this up just because I am confused
after reading your description on the previous issue and PR.
> Improved reliability in flush error
> -----------------------------------
>
> Key: IOTDB-1136
> URL: https://issues.apache.org/jira/browse/IOTDB-1136
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Core/Engine
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Critical
>
> current, when flush data error ,
> IoTDBDescriptor.getInstance().getConfig().setReadOnly(true), which will lead
> to MultiFileLogNodeManager#forceTask useless.
> But do not have a mechanism， which recover forceTask... which this will lead
> to write failed....
> so I will do this recover... Automatic fault recovery.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
