When changing the writing time series, why did the synchronization task of Apache IoTDB delayed before restarting?
I tested the data synchronization function of Apache IoTDB according to the official documentation. When I wrote data to server A, it can be synchronized to server B at first. However, when I changed the writing setting from root.db.d to root.db2.d, I found that the synchronization did not work. When I restarted server A, the data that was not synchronized before was successsfully synchronized.
When exporting data from Apache IoTDB, why did the `not allowed to write out-of-order data` error reported?
How should I solve this error when exporting data for "select * from root.** from Apache IoTDB? The error information is Cannot dump result because: Not allowed to write out-of-order data in timeseries root.hess_test.running.inverter.WL000001.WL2N1N10131001D9A1000005, time should later than 1706218688000. I did not set any ttl, and the directory data/datanode/data/unsequence, which should be the out-of-order data storage directory, is also empty. Therefore, why is this error reported and how should I deal with it?