[
https://issues.apache.org/jira/browse/IOTDB-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274194#comment-17274194
]
Chao Wang commented on IOTDB-1136:
----------------------------------
2. 一般我们考虑恢复机制适用于大多数失败场景，极端的失败场景（磁盘满等不可逆转）可以根据多次恢复间隔时间来判断是一般性失败，还是极端失败。
(1) 如果是极端失败，那么即使恢复过来也会很快失败，间隔短...
(2)一般性失败两次恢复间隔比较长...
2. 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.
(1) If it is an extreme failure, it will fail quickly even if it is recovered.
The interval is short.
(2) The interval between two recovery failures is long.
> 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)
