[
https://issues.apache.org/jira/browse/IGNITE-26101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-26101:
---------------------------------------
Description:
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:
# MG repair after upgrade
## Metastore is created (and flushed) on v1 for a cluster of 3 nodes (ABC); MG
leader is node A
## v2 nodes are started on the same work dirs (only for nodes BC; a is not
started)
## MG repair is performed to make B or C a leader
# Upgrade after MG repair (perform the same repair steps as above and then do
the upgrade of the remaining nodes)
was:
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
> Add Metastore compatibility tests before/after MG repair
> --------------------------------------------------------
>
> Key: IGNITE-26101
> URL: https://issues.apache.org/jira/browse/IGNITE-26101
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> 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 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:
> # MG repair after upgrade
> ## Metastore is created (and flushed) on v1 for a cluster of 3 nodes (ABC);
> MG leader is node A
> ## v2 nodes are started on the same work dirs (only for nodes BC; a is not
> started)
> ## MG repair is performed to make B or C a leader
> # Upgrade after MG repair (perform the same repair steps as above and then
> do the upgrade of the remaining nodes)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
