IGNITE-28671 Describe healthy cluster behavior in general tips guide#13130
Merged
Conversation
zstan
reviewed
May 14, 2026
zstan
reviewed
May 14, 2026
zstan
reviewed
May 14, 2026
|
nizhikov
reviewed
Jun 3, 2026
There was a problem hiding this comment.
Pull request overview
This PR updates the general performance tips documentation to include guidance on assessing Apache Ignite cluster health, and adjusts the page title wording to “General Performance Tips”.
Changes:
- Rename the document title from “Generic Performance Tips” to “General Performance Tips”.
- Add a new “How to assess cluster health” section describing practical signals and checks (cluster state/baseline,
idle_verify, rebalance convergence, queues, transactions/queries, persistence checkpoint pressure, and logs).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
zstan
reviewed
Jul 15, 2026
copilot' grammar changes Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
zstan
reviewed
Jul 20, 2026
Co-authored-by: Evgeniy Stanilovskiy <stanilovsky@gmail.com>
zstan
reviewed
Jul 23, 2026
Co-authored-by: Evgeniy Stanilovskiy <stanilovsky@gmail.com>
zstan
reviewed
Jul 24, 2026
Co-authored-by: Evgeniy Stanilovskiy <stanilovsky@gmail.com>
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
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.
Changes that have been made
What
Adds guidance for assessing Apache Ignite cluster health to the general performance tips documentation. The guide covers cluster state and membership, partition consistency, rebalancing, execution queues, transactions, Partition Map Exchanges, checkpoint pressure, failure handling, and optional CDC monitoring.
It also includes representative command output, log records, metric queries, and JConsole examples.
Why
Cluster health cannot be determined from a single metric or connectivity check. Operators need to evaluate several related signals and distinguish expected transient activity from conditions that require investigation.
This guidance provides a consolidated operational checklist and directs readers to the relevant configuration, monitoring, and recovery documentation.
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.