This is an automated email from the ASF dual-hosted git repository.
zstan pushed a commit to branch ignite-2.18
in repository https://gitbox.apache.org/repos/asf/ignite.git
The following commit(s) were added to refs/heads/ignite-2.18 by this push:
new 022fbe7e144 IGNITE-28742 Document page eviction monitoring (#13204)
022fbe7e144 is described below
commit 022fbe7e1446c1aab2f5a6720706a3634fbd686c
Author: ignitetcbot <[email protected]>
AuthorDate: Tue Jul 7 10:28:25 2026 +0300
IGNITE-28742 Document page eviction monitoring (#13204)
Codex co-authored-by: Dmitriy Pavlov <[email protected]>
(cherry picked from commit b31fadeb6b91d98c88d08cd7875584ffd1c47c79)
---
docs/_docs/memory-configuration/eviction-policies.adoc | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/docs/_docs/memory-configuration/eviction-policies.adoc
b/docs/_docs/memory-configuration/eviction-policies.adoc
index 9aee23c8b92..781b05598cb 100644
--- a/docs/_docs/memory-configuration/eviction-policies.adoc
+++ b/docs/_docs/memory-configuration/eviction-policies.adoc
@@ -48,6 +48,24 @@ If you don't use data regions, you have to explicitly add
default data region pa
By default, eviction starts when the overall RAM consumption by a region gets
to 90%.
Use the `DataRegionConfiguration.setEvictionThreshold(...)` parameter if you
need to initiate eviction earlier or later.
+=== Monitoring Page Eviction
+
+When page eviction starts due to a data region being under memory pressure,
Ignite sets the `EvictionsStarted` metric to `true` for that data region.
+This metric is relevant for in-memory data regions, where page eviction can
remove data from memory.
+It is available in the `io.dataregion.{data_region_name}` registry.
+After `EvictionsStarted` becomes `true`, it remains `true` until the node is
restarted.
+Use it together with `EvictionRate` to monitor whether eviction has started
and how actively pages are being evicted.
+
+Ignite also logs a warning when page-based eviction starts:
+
+[source,text]
+----
+Page-based evictions started. Consider increasing 'maxSize' on Data Region
configuration: <region_name>
+----
+
+The warning is logged once per data region.
+For monitoring, prefer the `EvictionsStarted` metric because monitoring tools
can use it directly without relying on log parsing.
+
Ignite supports two page selection algorithms:
* Random-LRU