...
We need to provide the ability to restore individual cache groups from an existing snapshot on an active cluster.
The overall process includes the following sequential steps:
...
If any of the nodes on which the snapshot was taken leave the cluster during the restore process, the process is aborted and all changes are rolled back (to achieve this, a special cache launch mode was introduced, if the node exits during the exchange, the process is rolled back).
// TBD
Sometimes the user is faced with the task of adding post-processing to the snapshot operation, for example, calculating the checksum of files, checking the consistency, etc. The same applies to the recovery procedure - the user should be able to check the consistency of files, checksums, etc. before restore them.
It is impossible to implement pre/post-processing using standard Ignite events. if a custom check detects a problem, the entire operation with the snapshot must be aborted.
It is recommended to add the ability to load SnapshotLifecycleListener user extensions that will implement custom checks.
// TBD
...