[
https://issues.apache.org/jira/browse/IGNITE-26106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-26106:
---------------------------------------
Priority: Minor (was: Major)
> Add CMG compatibility tests before/after CMG repair
> ---------------------------------------------------
>
> Key: IGNITE-26106
> URL: https://issues.apache.org/jira/browse/IGNITE-26106
> 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 CMG storage is flushed
> and the node is stopped, its binary is replaced with v2, the node is started.
> We must test the following scenarios:
> # CMG repair after upgrade
> ## CMG is created (and flushed) on v1 for a cluster of 3 nodes (ABC); CMG
> leader is node A
> ## v2 nodes are started on the same work dirs (only for nodes BC; a is not
> started)
> ## CMG repair is performed to make B or C a leader
> # Upgrade after CMG repair (perform the same repair steps as above and then
> do the upgrade)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
