[
https://issues.apache.org/jira/browse/RATIS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089114#comment-17089114
]
Hanisha Koneru commented on RATIS-850:
--------------------------------------
On second thoughts, purging only upto snapshotIndex always might not be a good
idea. Let's say the StateMachine takes snapshots after very large number of
transactions (For instance, the default snapshot threshold in Ozone Manager is
400,000). In this case, we would want to purge the logs even if the snapshot
does not contain an index but it has been committed on all peers.
> Allow log purge up to snapshot index
> ------------------------------------
>
> Key: RATIS-850
> URL: https://issues.apache.org/jira/browse/RATIS-850
> Project: Ratis
> Issue Type: Improvement
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
> Attachments: RATIS-850.001.patch, RATIS-850.002.patch
>
>
> Ratis logs are purged only up to the least commit index on all the peers. But
> if one peer is down, it stop log purging on all the peers. If the Ratis
> server takes snapshots, then we can purge logs up to the snapshot index even
> if some peer has not committed up to that index. When the peer rejoins the
> ring, instead of ratis logs, it can get the snapshot to catch up.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
