[
https://issues.apache.org/jira/browse/IOTDB-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialin Qiao reassigned IOTDB-3843:
----------------------------------
Assignee: Haiming Zhu
> Refine the using of setting read-only
> -------------------------------------
>
> Key: IOTDB-3843
> URL: https://issues.apache.org/jira/browse/IOTDB-3843
> Project: Apache IoTDB
> Issue Type: Improvement
> Reporter: Jialin Qiao
> Assignee: Haiming Zhu
> Priority: Major
>
> We now abuse the system read-only, which is a dangerous operation.
> Even worse, when system is set to read-only, I could not find why we set it
> to read-only, there is no related log.
>
> We only set read-only when losing data continuously, otherwise, we must store
> more data as we can.
>
> (1) In the IoTDBConfig.setReadOnly() function, if it receive a true, we need
> to log the stack trace with the information "change system mode to
> read-only". To avoid missing the log outside.
> if (readOnly)
> { logger.error("change system mode to read-only", new RuntimeException()); }
> (2) Check all places that set read-only, this is a dangerous operation in the
> deployment environment, and we should avoid using this if not necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
