[ https://issues.apache.org/jira/browse/RATIS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083774#comment-17083774 ]
Mukul Kumar Singh commented on RATIS-850: ----------------------------------------- [~hanishakoneru], This was done on Ozone's datanode to avoid cases where aggressive log purge will cause the log to be purged and this will trigger snapshot installation rather very frequently. > 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 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)