You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by ti...@apache.org on 2022/02/16 09:13:35 UTC

[ignite] branch ignite-2.12 updated (172f825 -> d648e99)

This is an automated email from the ASF dual-hosted git repository.

timoninmaxim pushed a change to branch ignite-2.12
in repository https://gitbox.apache.org/repos/asf/ignite.git.


    from 172f825  IGNITE-15902 Removed section irrelevant to Ignite. Fixes #9561
     new 9895ff8  IGNITE-15074 : Fix documentation for support encrypted snapshots (#9238)
     new d648e99  IGNITE-16517 Fix documentation for snapshot restore procedure (#9812)

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 docs/_docs/security/tde.adoc        |  4 +---
 docs/_docs/snapshots/snapshots.adoc | 29 +++++++++++++----------------
 2 files changed, 14 insertions(+), 19 deletions(-)

[ignite] 02/02: IGNITE-16517 Fix documentation for snapshot restore procedure (#9812)

Posted by ti...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

timoninmaxim pushed a commit to branch ignite-2.12
in repository https://gitbox.apache.org/repos/asf/ignite.git

commit d648e99e4252656e5142a7257cf99ca5da3f83e8
Author: Maxim Muzafarov <ma...@gmail.com>
AuthorDate: Thu Feb 10 19:35:44 2022 +0300

    IGNITE-16517 Fix documentation for snapshot restore procedure (#9812)
---
 docs/_docs/snapshots/snapshots.adoc | 26 +++++++++++---------------
 1 file changed, 11 insertions(+), 15 deletions(-)

diff --git a/docs/_docs/snapshots/snapshots.adoc b/docs/_docs/snapshots/snapshots.adoc
index 5456396..621d3f3 100644
--- a/docs/_docs/snapshots/snapshots.adoc
+++ b/docs/_docs/snapshots/snapshots.adoc
@@ -73,7 +73,7 @@ are not added into the snapshot as long as those are not required for the curren
 The previous example shows the snapshot created for the cluster running on the same physical machine. Thus, the whole
 snapshot is located in a single place. While in practice, all the nodes will be running on different machines having the
 snapshot data spread across the cluster. Each node keeps a segment of the snapshot with the data belonging to this particular node.
-The link:persistence/snapshots#restoring-from-snapshot[restore procedure] explains how to tether together all the segments during recovery.
+The link:snapshots/snapshots#restoring-from-snapshot[restore procedure] explains how to tether together all the segments during recovery.
 ====
 
 == Configuration
@@ -155,10 +155,18 @@ See the link:tools/control-script#checking-snapshot-consistency[Control Script]
 commands.
 
 == Restoring From Snapshot
-A snapshot can be restored either manually on a stopped cluster or automatically on an active cluster. Both procedures are described below.
+
+A snapshot can be restored either manually on a stopped cluster or automatically on an active cluster.
+Both procedures are described below, however, it is preferable to use the restore command from Control Script only.
 
 === Manual Snapshot Restore Procedure
-Stop the cluster, then replace persistence data and other files with the data from the snapshot, and restart the nodes.
+
+The snapshot structure is similar to the layout of the Ignite Native Persistence, so for the manual snapshot restore you must
+do a snapshot restore only on the same cluster with the same node `consistentId` and on the same topology on which a snapshot
+was taken. If you need to restore a snapshot on a different cluster or on a different cluster topology use the
+link:snapshots/snapshots#automatic-snapshot-restore-procedure[Automatic Snapshot Restore Procedure].
+
+In general, stop the cluster, then replace persistence data and other files with the data from the snapshot, and restart the nodes.
 
 The detailed procedure looks as follows:
 
@@ -171,18 +179,6 @@ The detailed procedure looks as follows:
     - Copy the files belonging to a node with the `{node_id}` from the snapshot into the `$IGNITE_HOME/work/` directory. If the `db/{node_id}` directory is not located under the Ignite `work` dir then you need to copy data files there.
 . Restart the cluster
 
-*Restore On Cluster of Different Topology*
-
-You may want to create a snapshot of an N-node cluster and use it to restore on an M-node cluster. The table below explains what options are supported:
-[cols="1,1",opts="header"]
-|===
-|Condition | Description
-|N == M | The *recommended* case. Create and use the snapshot on clusters of a similar topology.
-|N < M | Start the first N nodes of the M-node cluster and apply the snapshot. Add the rest of the M-cluster nodes to
-the topology and wait while the data gets rebalanced and indexes are rebuilt.
-|N > M | Unsupported.
-|===
-
 === Automatic Snapshot Restore Procedure
 
 The automatic restore procedure allows the user to restore cache groups from a snapshot on an active cluster by using the Java API or link:tools/control-script[command line script].

[ignite] 01/02: IGNITE-15074 : Fix documentation for support encrypted snapshots (#9238)

Posted by ti...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

timoninmaxim pushed a commit to branch ignite-2.12
in repository https://gitbox.apache.org/repos/asf/ignite.git

commit 9895ff85bac1a60c67bc072c971b27d942bae603
Author: Vladimir Steshin <vl...@gmail.com>
AuthorDate: Mon Feb 14 16:00:30 2022 +0300

    IGNITE-15074 : Fix documentation for support encrypted snapshots (#9238)
---
 docs/_docs/security/tde.adoc        | 4 +---
 docs/_docs/snapshots/snapshots.adoc | 3 ++-
 2 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/docs/_docs/security/tde.adoc b/docs/_docs/security/tde.adoc
index 5d3ce1e..5d060c0 100644
--- a/docs/_docs/security/tde.adoc
+++ b/docs/_docs/security/tde.adoc
@@ -14,8 +14,6 @@
 // limitations under the License.
 = Transparent Data Encryption
 
-WARNING: This feature is in beta and not recommended for use in production environments.
-
 == Overview
 Transparent data encryption (TDE) allows users to encrypt their data at rest.
 
@@ -43,7 +41,7 @@ Transparent Data Encryption has some limitations that you should be aware of bef
 
 *Snapshots and Recovery*
 
-* No support for snapshots. Snapshots are not encrypted and it's not possible to recover from a snapshot that includes an encrypted table or cache.
+* Encryption, changing of master key or cache group key are not allowed during snapshot operations.
 
 == Configuration
 To enable encryption in the cluster, provide a master key in the configuration of each server node. A configuration example is shown below.
diff --git a/docs/_docs/snapshots/snapshots.adoc b/docs/_docs/snapshots/snapshots.adoc
index 7b0e5f8..5456396 100644
--- a/docs/_docs/snapshots/snapshots.adoc
+++ b/docs/_docs/snapshots/snapshots.adoc
@@ -253,8 +253,9 @@ The snapshot procedure has some limitations that you should be aware of before u
 
 * Snapshotting of specific caches/tables is unsupported. You always create a full cluster snapshot.
 * Caches/tables that are not persisted in Ignite Persistence are not included into the snapshot.
-* Encrypted caches are not included in the snapshot.
+* Encrypted caches in the snapshot must be encrypted with the same master key.
 * You can have only one snapshotting operation running at a time.
+* The snapshot operation is prohibited during a master key change and/or cache group key change.
 * The snapshot procedure is interrupted if a server node leaves the cluster.
 
 If any of these limitations prevent you from using Apache Ignite, then select alternate snapshotting implementations for