w3ll1ngt commented on code in PR #13741:
URL: https://github.com/apache/ignite/pull/13741#discussion_r4446347080


##########
docs/_docs/persistence/native-persistence.adoc:
##########
@@ -368,5 +384,8 @@ The following table describes some properties of 
link:{javadoc_base_url}/org/apa
 |`walMode` | <<WAL Modes,Write-ahead logging mode>>. | `LOG_ONLY`
 
 | `walCompactionLevel` | WAL archive compression level. `1` indicates the 
fastest speed, and `9` indicates the best compression. | `1`
-|`maxWalArchiveSize`  | The maximum size (in bytes) the WAL archive can occupy 
on the file system. | Four times the size of the 
link:persistence/persistence-tuning#adjusting-checkpointing-buffer-size[checkpointing
 buffer].
+|`maxWalArchiveSize`  | The upper threshold (in bytes) of the WAL archive. 
When the archive reaches it, Ignite forcibly releases the reservations of the 
segments that the last completed checkpoint already covers, so that the cleanup 
can delete them. It is not a hard bound on the directory size. | 1 GiB
+|`minWalArchiveSize` | The threshold (in bytes) that makes segments eligible 
for cleanup. The cleanup runs in the background and removes the oldest segments 
while the archive stays above this value. Segments are removed as whole files, 
so the remaining size can be below it. | Half of `maxWalArchiveSize`
+|`walSegments` | The number of active WAL segments. The volume that holds the 
active WAL has to fit that many segments of `walSegmentSize` plus a rotation 
reserve. | `10`
+|`checkpointFrequency` | The interval between checkpoints, in milliseconds. A 
value that is too small produces frequent checkpoints and a large number of 
checkpoint markers. | `180000` (3 minutes)

Review Comment:
   just removed `too small` phrase and simlified the statement. Have no 
confidence in situations when you really need to change the default. idk



-- 
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]

Reply via email to