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

Aleksandr Polovtsev updated IGNITE-24822:
-----------------------------------------
    Description: 
Currently partition Raft snapshots are represented as the current persistent 
state of the partition storages. It is proposed to separately save information 
about the last successfully performed Raft snapshot. In other words, when JRaft 
invokes {{RaftGroupListener#onSnapshotSave}} we should save the snapshot meta 
of this snapshot in the TX storage.

This is needed as a part of the implementation of the algorithm described in 
IGNITE-24811.

  was:
Currently partition Raft snapshots are represented as the current persistent 
state of the partition storages. It is proposed to separately save information 
about the last successfully performed Raft snapshot. In other words, when JRaft 
invokes {{RaftGroupListener#onSnapshotSave}} we should save the snapshot meta 
in the TX storage for this snapshot.

This is needed as a part of the implementation of the algorithm described in 


> Persist last created Raft snapshot information
> ----------------------------------------------
>
>                 Key: IGNITE-24822
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24822
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksandr Polovtsev
>            Assignee: Aleksandr Polovtsev
>            Priority: Major
>              Labels: ignite-3
>
> Currently partition Raft snapshots are represented as the current persistent 
> state of the partition storages. It is proposed to separately save 
> information about the last successfully performed Raft snapshot. In other 
> words, when JRaft invokes {{RaftGroupListener#onSnapshotSave}} we should save 
> the snapshot meta of this snapshot in the TX storage.
> This is needed as a part of the implementation of the algorithm described in 
> IGNITE-24811.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to