[
https://issues.apache.org/jira/browse/IGNITE-26099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-26099:
---------------------------------------
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.
Then we make sure the Raft log of Metastore group gets truncated and join a new
node (in v2).
After that, second node should function correctly (we could trigger a rebalance
to make sure).
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.
After that, the node should function correctly (we could trigger a rebalance to
make sure).
> Add Metastore snapshot file compatibility test
> ----------------------------------------------
>
> Key: IGNITE-26099
> URL: https://issues.apache.org/jira/browse/IGNITE-26099
> 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.
> Then we make sure the Raft log of Metastore group gets truncated and join a
> new node (in v2).
> After that, second node should function correctly (we could trigger a
> rebalance to make sure).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
