You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2021/08/22 15:05:00 UTC

[jira] [Resolved] (RATIS-1390) Bootstrapping Peer should always try to install a snapshot the first time

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

Tsz-wo Sze resolved RATIS-1390.
-------------------------------
    Fix Version/s: 2.2.0
       Resolution: Fixed

I haver merged the pull request.  Thanks, [~hanishakoneru]!

> Bootstrapping Peer should always try to install a snapshot the first time
> -------------------------------------------------------------------------
>
>                 Key: RATIS-1390
>                 URL: https://issues.apache.org/jira/browse/RATIS-1390
>             Project: Ratis
>          Issue Type: Improvement
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>            Priority: Major
>             Fix For: 2.2.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> When a peer is bootstrapping and joins the Ratis ring via SetConf request, the Leader adds the peer to the sender list and sends it either the append log entries or the snapshot or a notification to install snapshot via State Machine. The leader sends the snapshot only when some or all of the ratis logs have been purged. 
> The snapshot is maintained by the State Machine and as such could contain information not present in the Ratis logs (for example Ozone's OzoneManager StateMachine maintains the snapshot as a DB file and it could contain information which cannot be constructed just using the Ratis logs - HDDS-5338). 
> To avoid this scenario, this Jira proposes that whenever a new peer is bootstrapping, the leader should send an install snapshot request at least once.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)