...
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
public interface IgniteSnapshot { /** * @return List of all known snapshots. */ public List<String> getSnapshots(); /** * Create a consistent copy of all persistence cache groups from the whole cluster. * * @param name Snapshot name. * @return Future which will be completed when a process ends. */ public IgniteFuture<Void> createSnapshot(String name); } |
...
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
package org.apache.ignite.mxbean; /** * Snapshot features MBean. */ @MXBeanDescription("MBean that provides access for snapshot features.") public interface SnapshotMXBean { /** * Gets all created snapshots on the cluster. * * @return List of all known snapshots. */ @MXBeanDescription("List of all known snapshots.") public List<String> getSnapshots(); /** * Create the cluster-wide snapshot with given name. * * @param snpName Snapshot name to created. * @see IgniteSnapshot#createSnapshot(String) (String) */ @MXBeanDescription("Create cluster-wide snapshot.") public void createSnapshot(@MXBeanParameter(name = "snpName", description = "Snapshot name.") String snpName); } |
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
# Starts cluster snapshot operation. control.sh --snapshot ERIB_23012020 # Display all known cluster snapshots. control.sh --snapshot -list |
...
Internal API which allows to request and receive the required snapshot of cache groups from a remote. Used as a part of IEP-28: Rebalance peer-2-peer to send created local snapshot to the remote (demander) node.
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
/** * @param parts Collection of pairs group and appropriate cache partition to be snapshot. * @param rmtNodeId The remote node to connect to. * @param partConsumer Received partition handler. * @return Future which will be completed when requested snapshot fully received. */ public IgniteInternalFuture<Void> createRemoteSnapshot( UUID rmtNodeId, Map<Integer, Set<Integer>> parts, BiConsumer<File, GroupPartitionId> partConsumer); |
...
The snapshot procedure stores all internal files (binary meta, marshaller meta, cache group data files, and cache group configuration) the same directory structure way as the Apache Ignite does with preserving configured consistent node id.
To restore a cluster from snapshot user must manually copy all snapshot data files to the IGNITE_HOME/work
directory pay 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
|
// Describe project risks, such as API or binary compatibility issues, major protocol changes, etc.
...
http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Hot-cache-backup-td41034.html
...
// Links or report with relevant JIRA tickets.