Skip to content

IGNITE-23645 Document eviction completion logs #13522

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ignitetcbot wants to merge 1 commit into
base: master
Choose a base branch
from
Open

IGNITE-23645 Document eviction completion logs #13522

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/_docs/perf-and-troubleshooting/general-perf-tips.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -234,6 +234,11 @@ You can also track link:monitoring-metrics/new-metrics#cache-groups[node-local c
* `LocalNodeRentingPartitionsCount`
* `LocalNodeRentingEntriesCount`

When partition eviction finishes for a cache group, Ignite writes an `Eviction completed` message to the node log.
`Eviction completed successfully` means that the listed `evictedParts` were removed.
`Eviction completed with failures` includes `nonEvictedParts`; check these partitions together with the `RENTING` rows and the `LocalNodeRenting*` metrics.
The message also includes the cache group name in `grp` and the eviction reason.

Use the link:monitoring-metrics/system-views#partition_states[PARTITION_STATES] system view to check partition states:

* `OWNING`: the node is the current primary or backup owner.
Expand Down