IGNITE-28742 Document page eviction monitoring#13204
Open
ignitetcbot wants to merge 2 commits into
Open
Conversation
oleg-vlsk
reviewed
Jun 18, 2026
|
|
||
| === Monitoring Page Eviction | ||
|
|
||
| When page eviction starts because a data region is under memory pressure, Ignite sets the `EvictionsStarted` metric to `true` for that data region. |
Contributor
There was a problem hiding this comment.
“When page eviction starts because a data region is under memory pressure...” sounds a bit unnatural. I would suggest rephrasing it as:
“When page eviction starts due to a data region being under memory pressure...”
|
|
||
| When page eviction starts because a data region is under memory pressure, Ignite sets the `EvictionsStarted` metric to `true` for that data region. | ||
| The metric is available in the `io.dataregion.{data_region_name}` registry. | ||
| Use it together with `EvictionRate` to monitor whether eviction has started and how actively pages are being evicted. |
Contributor
There was a problem hiding this comment.
It is probably worth mentioning that page eviction with potential data loss, and therefore this metric, is relevant for in-memory clusters rather than persistent ones.
|
|
||
| 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. | ||
|
|
Contributor
There was a problem hiding this comment.
It would also be useful to mention that once eviction starts, the EvictionsStarted metric remains set to true until the node is restarted.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thank you for submitting the pull request to the Apache Ignite.
In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:
The Contribution Checklist
The description explains WHAT and WHY was made instead of HOW.
The following pattern must be used:
IGNITE-XXXX Change summarywhereXXXX- number of JIRA issue.(see the Maintainers list)
the
green visaattached to the JIRA ticket (see tabPR Checkat TC.Bot - Instance 1 or TC.Bot - Instance 2)Notes
If you need any help, please email dev@ignite.apache.org or ask anу advice on http://asf.slack.com #ignite channel.