[
https://issues.apache.org/jira/browse/IOTDB-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tian Jiang reassigned IOTDB-915:
--------------------------------
Assignee: Houliang Qi
> [Distributed] Merge StableEntryManager into CommittedLogManager
> ---------------------------------------------------------------
>
> Key: IOTDB-915
> URL: https://issues.apache.org/jira/browse/IOTDB-915
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Core/Cluster
> Reporter: Tian Jiang
> Assignee: Houliang Qi
> Priority: Major
> Labels: cluster, log-management, persistency
>
> The current version of CommittedLogManager only holds a small number of logs,
> as it only uses the persistent storage (namely the StableEntryManager) as a
> measure of recovery, not to extend its storage ability. The result is that
> when one follower is down, its difference from the leader will soon exceed
> the capability of the CommittedLogManager, which further results in a
> snapshot catch-up, and it is time-consuming.
> The idea is to merge StableEntryManager into CommittedLogManager, all
> committed logs should go to the persistent storage (unless persistency is
> disabled), and only the newest part of the logs will stay in memory. And
> CommittedLogManager should be able to read logs from the disk for catch-ups,
> provided they are not physically removed. Thus, the retention policy of
> memory logs and disk logs should be reconsidered.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
