You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@iotdb.apache.org by "Houliang Qi (Jira)" <ji...@apache.org> on 2020/06/09 07:37:00 UTC

[jira] [Commented] (IOTDB-723) [Distributed] Decide a log discarding policy

    [ https://issues.apache.org/jira/browse/IOTDB-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128959#comment-17128959 ] 

Houliang Qi commented on IOTDB-723:
-----------------------------------

IMO, we can combine time-based method and number-based method together. Each server periodically triggers the operation to check the deletion of the log. If the distance between the last deletion log index and  the current maximum applied index exceeds a certain threshold, you can perform the deletion operation, otherwise do nothing.

> [Distributed] Decide a log discarding policy
> --------------------------------------------
>
>                 Key: IOTDB-723
>                 URL: https://issues.apache.org/jira/browse/IOTDB-723
>             Project: Apache IoTDB
>          Issue Type: Improvement
>          Components: Core/Cluster
>            Reporter: Tian Jiang
>            Priority: Major
>              Labels: cluster, log-serialization
>
> Although the committed raft logs are currently serialized, we have not decided on a policy of when to remove them.
> The possible alternatives may be a time-based method or a number-based method, but any better ideas are welcomed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)