THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
To restore a cluster from snapshot user must manually copy do the following:
- Remove data from the checkpoint, wal, binary_meta, marshaller directories.
- Copy all snapshot data files to the
IGNITE_HOME/work
...
- directory with paying attention to consistent node ids.
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
maxmuzaf@TYE-SNE-0009931 ignite % tree work
work
└── snapshots
└── backup23012020
├── binary_meta
│ ├── snapshot_IgniteClusterSnapshotSelfTest0
│ ├── snapshot_IgniteClusterSnapshotSelfTest1
│ └── snapshot_IgniteClusterSnapshotSelfTest2
├── db
│ ├── snapshot_IgniteClusterSnapshotSelfTest0
│ │ ├── cache-default
│ │ │ ├── cache_data.dat
│ │ │ ├── part-0.bin
│ │ │ ├── part-2.bin
│ │ │ ├── part-3.bin
│ │ │ ├── part-4.bin
│ │ │ ├── part-5.bin
│ │ │ └── part-6.bin
│ │ └── cache-txCache
│ │ ├── cache_data.dat
│ │ ├── part-3.bin
│ │ ├── part-4.bin
│ │ └── part-6.bin
│ ├── snapshot_IgniteClusterSnapshotSelfTest1
│ │ ├── cache-default
│ │ │ ├── cache_data.dat
│ │ │ ├── part-1.bin
│ │ │ ├── part-3.bin
│ │ │ ├── part-5.bin
│ │ │ ├── part-6.bin
│ │ │ └── part-7.bin
│ │ └── cache-txCache
│ │ ├── cache_data.dat
│ │ ├── part-1.bin
│ │ ├── part-5.bin
│ │ └── part-7.bin
│ └── snapshot_IgniteClusterSnapshotSelfTest2
│ ├── cache-default
│ │ ├── cache_data.dat
│ │ ├── part-0.bin
│ │ ├── part-1.bin
│ │ ├── part-2.bin
│ │ ├── part-4.bin
│ │ └── part-7.bin
│ └── cache-txCache
│ ├── cache_data.dat
│ ├── part-0.bin
│ └── part-2.bin
└── marshaller
17 directories, 30 files
|
Snapshot requirements
- Users must have the ability to create a snapshot under the load without cluster deactivation.
- The snapshot process must not block for a long time any of the user transactions (short-time blocks are acceptable).
- The snapshot process must allow creating a data snapshot on each node and transfer it to any of the remote nodes for internal cluster needs.
Process overview
...
- The created snapshot at the cluster-level must be fully consistent from cluster-wide terms, there should not be any incomplete transactions inside.
- The snapshot of each node must be consistent – cache partitions, binary meta, etc. must not have unnecessary changes.
Snapshot process
With respect to the cluster-wide snapshot operation, the process of creating a copy of user data can be split into the following high-level steps:
- Start a cluster-wide snapshot operation using any of the available public API.
- Each node will receive such an event and start a local snapshot task which must create a consistent copy of available user data.
- Collect the results of performing local snapshot tasks from each node and send the results back to the user.
The Distributed Process is used to complete steps [1, 3]. To achieve the step [2] a new SnapshotFutureTask must be developed.
Cluster snapshot
Local snapshot
Remote snapshot
Limitations
Risks and Assumptions
...
Overview
Content Tools
Apps