[
https://issues.apache.org/jira/browse/IOTDB-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274195#comment-17274195
]
Xiangdong Huang commented on IOTDB-1136:
----------------------------------------
> Non-regular time series will cause errors.
It is not acceptable that making IoTDB dead if someone writes some incorrect
data.
> but do not deal Out-of-order.
IMO, we should handle this. is there problems by just putting out of order data
to unseq folder?
> current encoding algorithm:
Current implementation may be incorrect. but I think we do not need to change
our design according to current implementation.
https://lists.apache.org/thread.html/f612326ca8708981b5a2da29f52b826105bbb55dc840281c5bf6af4f%40%3Cdev.iotdb.apache.org%3E
has some design discussion (I am not sure whether it has considered the out of
order case).
> 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)
