[
https://issues.apache.org/jira/browse/IGNITE-24466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954968#comment-17954968
]
Roman Puchkovskiy commented on IGNITE-24466:
--------------------------------------------
Upgrade scenarios. v1 is version before upgrade, v2 is version after upgrade. #
Partition storage
## aipersist works (all data written in v1 can be read in v2; including
overwritten versions; deleted data cannot be read)
### when there were no unmerged delta-files in v1
### when there were unmerged delta-files
### when unmerged delta-files remain from v1 and we start creating new delta
files immediately after starting on v2
## rocksdb
### we can vary number of levels in LSMT
## aimem (it has its Raft log)
### with or without spillout to disk
## (Re)application of commands (saved in v1) from Raft log (when running on v2)
### Reapplication (on the same node)
### Application to another node
## FST started in v1 (with a Raft snapshot) does not break anything on the
accepting side after starting on v2 and starting FST from scratch
# Metastorage
## Base test (wrote on v1, start on v2)
## Snapshot file format (create on v1, then start another node on v2 and
install the snapshot from old file to new node)
## Reapplication of commands (saved in v1) from Raft log (when running on v2)
## Interrelation with MG Disaster Recovery
### Disaster recovery, then upgrade
### Upgrade, then disaster recovery
## Compaction functions after upgrade
# CMG
## Basic test
## Restoration of a snapshot file created in v1
### of the node itself after upgrade
### of a new node with v2 that joins after upgrade
## Reapplication of v1 Raft commands in v2
## Interrelation with CMG Disaster Recovery
# Vault - reading keys saved in v1
# Indices
## Indices that finished being built in v1 are still available in v2
## Index build started (but not finished) in v1 gets finished in v2
successfully
# Tests for all Raft command types serialization
(edited)
> Add Storage format compatibility tests
> --------------------------------------
>
> Key: IGNITE-24466
> URL: https://issues.apache.org/jira/browse/IGNITE-24466
> Project: Ignite
> Issue Type: Task
> Components: persistence
> Reporter: Pavel Tupitsyn
> Priority: Critical
> Labels: ignite-3
> Fix For: 3.1
>
>
> Add tests to ensure that new Ignite versions can start with storage files
> from older versions (restart cluster with new AI version, keep the data).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
