[IGNITE-17983] Fix work with the last applied index in RAFT

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 3.0
• Labels: ignite-3
• Epic Link: Storage support for Rebalancing
• Assignee: Kirill Tkalenko
• Reporter: Kirill Tkalenko
• Reviewer: Ivan Bessonov
• Created: 26/Oct/22 14:55
• Updated: 04/Sep/24 16:19
• Resolved: 28/Oct/22 11:54

Description

At the moment, MvPartitionStorage and TxStateStorage are used for a partition raft group, while only MvPartitionStorage#persistedIndex of MvPartitionStorage#lastAppliedIndex is used, which is not correct.

On recovery, we need to use a minimum of MvPartitionStorage#lastAppliedIndex and TxStateStorage#lastAppliedIndex so as not to lose data for one of the storage.

When taking a snapshot for a full rebalance, we should use the maximum of MvPartitionStorage#lastAppliedIndex and TxStateStorage#lastAppliedIndex so that we can load up-to-date data from the leader.

Etc.

Issue Links

• duplicates: IGNITE-17302 Raft listener multi-storage support
• links to: GitHub Pull Request #1262