[
https://issues.apache.org/jira/browse/IGNITE-18079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-18079:
---------------------------------------
Description:
Currently, the code implementing sending and receiving of snapshots is already
there. Some scenarios need to be implemented:
# Node that has data restarts successfully (trivial, but should make sure that
'startup snapshot' is 'applied' correctly)
# Start a cluster of 3 nodes, stop one of them, add some data, provoke the
lagging node to restore itself from a snapshot, start it, make sure it catches
up
# Test that 'taking' snapshots does not interfere with normal functioning and
feeding followers with snapshots
# Test that a node that catches up using a snapshot gets updates happening
concurrently with snapshot streaming, applied in the correct order
# Test that, if a snapshot installation fails in the middle, the recipient
node data is still consistent
was:
Currently, the code implementing sending and receiving of snapshots is already
there. Some scenarios need to be implemented:
# Node that has data restarts successfully (trivial, but should make sure that
'startup snapshot' is 'applied' correctly)
# Start a cluster of 3 nodes, stop one of them, add some data, provoke the
lagging node to restore itself from a snapshot, start it, make sure it catches
up
# Test that 'taking' snapshots does not interfere with normal functioning and
feeding followers with snapshots
# Test that a node that catches up using a snapshot gets updates happening
concurrent with snapshot streaming, applied in the correct order
> Integrate RAFT streaming snapshots
> ----------------------------------
>
> Key: IGNITE-18079
> URL: https://issues.apache.org/jira/browse/IGNITE-18079
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, the code implementing sending and receiving of snapshots is
> already there. Some scenarios need to be implemented:
> # Node that has data restarts successfully (trivial, but should make sure
> that 'startup snapshot' is 'applied' correctly)
> # Start a cluster of 3 nodes, stop one of them, add some data, provoke the
> lagging node to restore itself from a snapshot, start it, make sure it
> catches up
> # Test that 'taking' snapshots does not interfere with normal functioning
> and feeding followers with snapshots
> # Test that a node that catches up using a snapshot gets updates happening
> concurrently with snapshot streaming, applied in the correct order
> # Test that, if a snapshot installation fails in the middle, the recipient
> node data is still consistent
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
