[
https://issues.apache.org/jira/browse/IGNITE-26096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-26096:
---------------------------------------
Priority: Minor (was: Major)
> Verify interrupted Raft snapshot installation compatibility
> -----------------------------------------------------------
>
> Key: IGNITE-26096
> URL: https://issues.apache.org/jira/browse/IGNITE-26096
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Minor
> Labels: ignite-3
>
> Legend: v1 is original version (3.0), v2 is current version (version from
> main branch).
> It is supposed that data is written in v1, then the storage is flushed and
> the node is stopped, its binary is replaced with v2, the node is started.
> Here is the scenario:
> # Originally, while on v1, have just 1 node in the cluster, so the
> replication factor is 1
> # Make sure the log is truncated while still on v1 (so that any node later
> will need a Raft snapshot to be installed to it to get the partition data)
> # While still on v2, join one more node
> # Change replication factor to 2
> # Wait for replication via Raft snapshot to start; don't let it finish the
> data transfer
> # Stop the receiving node
> # Start both nodes on v2
> # Verify that the new node will still get all the data from the original node
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
