Hi all,
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. This pr[1] is intend to solve the problems, the design documents are listed here[2], any comments are welcome. [1] https://github.com/apache/iotdb/pull/1865 [2] https://cwiki.apache.org/confluence/display/IOTDB/Add+raft+log+persist+mechanism+and+use+persist+log+to+catch+up Thanks, --------------------------------------- Houliang Qi
