[
https://issues.apache.org/jira/browse/IGNITE-28742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18094234#comment-18094234
]
Dmitry Pavlov commented on IGNITE-28742:
----------------------------------------
[~oleg_vlsk] thank you for review
master commit -
https://github.com/apache/ignite/commit/b31fadeb6b91d98c88d08cd7875584ffd1c47c79
[~zstan] could you please consider cherry-picking to 2.18?
> Document page eviction start monitoring and per-data-region warning behavior
> ----------------------------------------------------------------------------
>
> Key: IGNITE-28742
> URL: https://issues.apache.org/jira/browse/IGNITE-28742
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: Ignite TC Bot
> Assignee: Ignite TC Bot
> Priority: Major
> Labels: documentation, eviction, ise, metrics
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Documentation should explain how to monitor page eviction start after
> IGNITE-28085 and IGNITE-28099.
> The EvictionsStarted metric is already listed in the Data Region metrics
> table, but the user documentation does not explain the operational scenario:
> * EvictionsStarted becomes true for the affected DataRegion when page
> eviction starts due to memory pressure.
> * EvictionRate can be used together with EvictionsStarted to monitor ongoing
> page eviction activity.
> * The warning 'Page-based evictions started. Consider increasing maxSize on
> Data Region configuration: <region_name>' is logged once per DataRegion.
> * For monitoring, EvictionsStarted should be preferred over log parsing
> because it identifies the affected DataRegion directly.
> Suggested location: docs/_docs/memory-configuration/eviction-policies.adoc.
> Context: related tickets IGNITE-24992, IGNITE-28085, IGNITE-28099.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
