ignitetcbot commented on code in PR #13204:
URL: https://github.com/apache/ignite/pull/13204#discussion_r3496847694
##########
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 and the data must be reloaded later.
+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 it identifies the
affected data region directly and does not depend on log parsing.
Review Comment:
@oleg-vlsk could you please check updates?
--
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]
