[
https://issues.apache.org/jira/browse/IOTDB-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702507#comment-17702507
]
Haiming Zhu commented on IOTDB-5703:
------------------------------------
current timed_flush mechanism uses memtable create time as the criteria, we
should find a new method to use the last write time as the criteria.
> Memtable won't be flushed for a long while even if the time_partition is
> inactive
> ---------------------------------------------------------------------------------
>
> Key: IOTDB-5703
> URL: https://issues.apache.org/jira/browse/IOTDB-5703
> Project: Apache IoTDB
> Issue Type: Improvement
> Reporter: Jinrui Zhang
> Assignee: Haiming Zhu
> Priority: Major
>
> *Description*
> During our test, we found that the memtable of some time partition won't be
> flushed even if there is no data insertion towards the time partition.
> *Impaction*
> If the memtable is not flushed, there will be a unclosed tsfile inside the
> time partition, which will block the inner compaction of this time partition
> *Solution*
> We do have a timed flush strategy but it seems it is not working now. We need
> to fix it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
