Nikita-tech-writer commented on a change in pull request #9624:
URL: https://github.com/apache/ignite/pull/9624#discussion_r761800112
##########
File path: docs/_docs/snapshots/snapshots.adoc
##########
@@ -76,16 +76,25 @@ snapshot data spread across the cluster. Each node keeps a
segment of the snapsh
The link:persistence/snapshots#restoring-from-snapshot[restore procedure]
explains how to tether together all the segments during recovery.
====
-== Configuring Snapshot Directory
+== Configuration
+
+=== Snapshot Directory
By default, a segment of the snapshot is stored in the work directory of a
respective Ignite node and uses the same storage
media where Ignite Persistence keeps data, index, WAL, and other files. Since
the snapshot can consume as much space as
-already taken by the persistence files and can affect your applications'
performance by sharing the disk I/O with the
+already taken by the persistence files and can affect your application's
performance by sharing the disk I/O with the
Ignite Persistence routines, it's suggested to store the snapshot and
persistence files on different media.
See the
link:persistence/snapshot-directory#configuring-snapshot-directory[Configuring
Snapshot Directory] page for
configuration examples.
+=== Snapshot Execution Pool
+
+By default, the snapshot thread pool size has value `4`. Decreasing the number
of threads involving into snapshot creation will
+increase the total amount of time the snapshot being taking, however, this
will keep the disk load within reasonable limits.
Review comment:
```suggestion
By default, the snapshot thread pool size has a value of `4`. Decreasing the
number of threads involved in the snapshot creation process
increases the total amount of time for taking a snapshot. However, this
keeps the disk load within reasonable limits.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
