From bbb042d11b64a8a57c12626ed09914dd83c1e4fc Mon Sep 17 00:00:00 2001
From: ignitetcbot <43213589+ignitetcbot@users.noreply.github.com>
Date: Wed, 26 Aug 2026 20:58:32 +0300
Subject: [PATCH] IGNITE-23645 Document eviction completion logs

---
 docs/_docs/perf-and-troubleshooting/general-perf-tips.adoc | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/_docs/perf-and-troubleshooting/general-perf-tips.adoc b/docs/_docs/perf-and-troubleshooting/general-perf-tips.adoc
index 4cab9e9c78ab1..52249fec54a1c 100644
--- a/docs/_docs/perf-and-troubleshooting/general-perf-tips.adoc
+++ b/docs/_docs/perf-and-troubleshooting/general-perf-tips.adoc
@@ -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.