[
https://issues.apache.org/jira/browse/IGNITE-26100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029744#comment-18029744
]
Evgeny Stanilovsky commented on IGNITE-26100:
---------------------------------------------
discussed - no need to cherry-pick into ignite-3.1.0
> Add Metastore Raft log compatibility test
> -----------------------------------------
>
> Key: IGNITE-26100
> URL: https://issues.apache.org/jira/browse/IGNITE-26100
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Filipp Shergalis
> Priority: Critical
> Labels: ignite-3, release-3.1.0-blocker
> Fix For: 3.1
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> 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 Metastore storage is
> flushed and the node is stopped, its binary is replaced with v2, the node is
> started.
> We must test the following scenarios:
> # Reapplication of a log (written in v1) on v2 goes correctly. We could do
> the following:
> ## Make sure the v1 log is complete (no prefix truncation happens)
> ## Clean the Metastore storage while the node is offline
> ## Start on v2 and make sure the Metastore recovers after node recovery (we
> can verify this by triggering a rebalance and making sure it finishes
> correctly)
> # Application of a log (written on v1) by a leader on v2 to another node (a
> learner) also on v2 goes correctly. We might need the following to test this:
> ## Make sure the v1 log is complete (no prefix truncation happens)
> ## Originally, while on v1, have just 1 node in the cluster
> ## After we start on v2, join one more node (on v2)
> ## Wait for replication to finish
> ## Verify the Metastore got replicated correctly
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
