[ https://issues.apache.org/jira/browse/IGNITE-17983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirill Tkalenko reassigned IGNITE-17983: ---------------------------------------- Assignee: Kirill Tkalenko > Fix work with the last applied index in RAFT > -------------------------------------------- > > Key: IGNITE-17983 > URL: https://issues.apache.org/jira/browse/IGNITE-17983 > Project: Ignite > Issue Type: Improvement > Reporter: Kirill Tkalenko > Assignee: Kirill Tkalenko > Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)