You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Mukul Kumar Singh (JIRA)" <ji...@apache.org> on 2019/05/28 18:19:00 UTC
[jira] [Updated] (RATIS-563) Purge logs after snapshot only after
all the nodes have caught up with the index
[ https://issues.apache.org/jira/browse/RATIS-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mukul Kumar Singh updated RATIS-563:
------------------------------------
Summary: Purge logs after snapshot only after all the nodes have caught up with the index (was: Purge logs after snapshot only after all the nodes have catught up with the index)
> Purge logs after snapshot only after all the nodes have caught up with the index
> --------------------------------------------------------------------------------
>
> Key: RATIS-563
> URL: https://issues.apache.org/jira/browse/RATIS-563
> Project: Ratis
> Issue Type: Bug
> Components: snapshot
> Affects Versions: 0.3.0
> Reporter: Mukul Kumar Singh
> Assignee: Tsz Wo Nicholas Sze
> Priority: Major
> Attachments: r563_20190522.patch, r563_20190524.patch, r563_20190528.patch, r563_20190528b.patch
>
>
> Leader will purge the snapshot after applying a transaction. A transaction is applied after a majority has been reached. This means that a slow follower will request for a transaction which has already been purged and for this transaction to catchup the leader has to transfer the snapshot. This can be detrimental for the performance while replicating.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)