[
https://issues.apache.org/jira/browse/IGNITE-24486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-24486:
---------------------------------------
Description:
Here are the scenarios:
# After MG had been repaired, the following functionality should be restored:
## KV operations
## SQL DML/query operations
## DDL operations
# If, during MG repair, the Repair Conductor gets killed before it gets a
BecomeMetastorageLeaderMessage, the MG repair should not proceed after starting
up the node again
# A node whose Metastorage lags too much behind the Metastorage of the MG
leader (that is, the leader has already compacted away all revisions that are
present on the node) cannot join (this might be blocked by IGNITE-20166)
> Add missing integration tests for MG disaster recovery
> ------------------------------------------------------
>
> Key: IGNITE-24486
> URL: https://issues.apache.org/jira/browse/IGNITE-24486
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> Here are the scenarios:
> # After MG had been repaired, the following functionality should be restored:
> ## KV operations
> ## SQL DML/query operations
> ## DDL operations
> # If, during MG repair, the Repair Conductor gets killed before it gets a
> BecomeMetastorageLeaderMessage, the MG repair should not proceed after
> starting up the node again
> # A node whose Metastorage lags too much behind the Metastorage of the MG
> leader (that is, the leader has already compacted away all revisions that are
> present on the node) cannot join (this might be blocked by IGNITE-20166)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
