[jira] [Updated] (RATIS-70) Code refactoring on RaftLogCache

["Jing Zhao (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RATIS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jing Zhao updated RATIS-70:
---------------------------
    Description: The current RaftLogCache consists of LogSegment, and logSegment consists of log entries. Instead of directly storing all the log entries, we should separate the term/index/offset information and the entry content information. The former part is more like the index information and can be always kept in the memory. The entry content part can later be evicted from the memory based on eviction policies.  (was: In this jira we do some code refactoring on RaftLogCache. More specifically, we will let RaftLogCache only expose interfaces about log entries.)

> Code refactoring on RaftLogCache
> --------------------------------
>
>                 Key: RATIS-70
>                 URL: https://issues.apache.org/jira/browse/RATIS-70
>             Project: Ratis
>          Issue Type: Sub-task
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>
> The current RaftLogCache consists of LogSegment, and logSegment consists of log entries. Instead of directly storing all the log entries, we should separate the term/index/offset information and the entry content information. The former part is more like the index information and can be always kept in the memory. The entry content part can later be evicted from the memory based on eviction policies.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)