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


##########
docs/_docs/persistence/native-persistence.adoc:
##########
@@ -207,11 +213,21 @@ If a node is terminated abruptly during update 
operations, it is very likely tha
 
 
 === WAL Archive
-The WAL archive is used to store WAL segments that may be needed to recover 
the node after a crash. The number of segments kept in the archive is such that 
the total size of all segments does not exceed the specified size of the WAL 
archive.
+The WAL archive is used to store WAL segments that may be needed to recover 
the node after a crash. The number of segments kept in the archive is defined 
by the cleanup rules described below.
+
+By default, the maximum size of the WAL archive is `maxWalArchiveSize`, whose 
default value is 1 GiB. You can change that value in the <<Configuration 
Properties,configuration>>.
+
+Cleanup starts when the archive exceeds `minWalArchiveSize`, not 
`maxWalArchiveSize`. By default, `minWalArchiveSize` is half of 
`maxWalArchiveSize`, that is 512 MiB.
+The cleanup runs asynchronously in the background. It removes the oldest 
segments, stopping at the last completed checkpoint and at the segments that 
are reserved by a running checkpoint or by a reader. It removes whole segments 
while the archive stays above the threshold, so the remaining size can end up 
below it.
+
+`maxWalArchiveSize` is the upper threshold, and it is not a hard bound on the 
directory size. When the archive reaches it, Ignite forcibly releases the 
reservations of the segments that the last completed checkpoint already covers. 
This allows cleanup of older segments. Archive usage can still exceed 
`maxWalArchiveSize` while segments are needed for recovery.

Review Comment:
   thx!



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