Update troubleshooting-upgrades.md - #8051
Merged
Merged
Conversation
👋 Per [private link](elastic/sdh-elasticsearch#10214 (comment)) adding back in an earlier sentence that got moved to main upgrade doc.
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Contributor
🔍 Preview links for changed docs |
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
Contributor
There was a problem hiding this comment.
Docs review summary
Focus areas
- Style and clarity: Two small grammar issues in the new/changed text — a subject-verb agreement slip in the new list item and a missing article in the rewritten shard-allocation explanation. See inline comments.
- Jargon: No unexplained Elastic-internal jargon in the changed lines.
- Frontmatter and applies_to: Unchanged by this PR; no issues introduced.
- Content type fit: Troubleshooting content type is preserved; the added sentence and list item fit the existing Symptoms/Resolution structure.
- Contradictions: No contradictions found.
- Parent issue satisfaction: Not applicable — no linked parent issue found.
Nits
- Vale flagged "for the duration of" (line 19) and a semicolon (line 149) as pre-existing wordiness/style suggestions, but neither is part of this PR's diff.
Notes
- Review scope covered only the single eligible changed markdown file,
troubleshoot/elasticsearch/troubleshooting-upgrades.md.
Generated by Docs review agent for #8051 · sonnet50 · 35.9 AIC · ⌖ 3.9 AIC · ⊞ 17.7K
| * `cannot allocate replica shard to a node with version [X.X.X] since this is older than the primary version [Y.Y.Y]` | ||
|
|
||
| If you encounter any of these, continue upgrading your nodes. The data allocates as more nodes reach the later version. | ||
| Primary shards assigned to a node running the later version cannot have their replicas assigned to nodes with the older version. If replica shard allocations are blocked due to insufficient eligible nodes on later version, continue upgrading your nodes to resolve the preceding errors. |
Contributor
There was a problem hiding this comment.
"nodes on later version" is missing an article. Use "on the later version" for consistency with the rest of the page, which always pairs "the" with "later version" and "earlier version".
Suggested change
| Primary shards assigned to a node running the later version cannot have their replicas assigned to nodes with the older version. If replica shard allocations are blocked due to insufficient eligible nodes on later version, continue upgrading your nodes to resolve the preceding errors. | |
| Primary shards assigned to a node running the later version cannot have their replicas assigned to nodes with the older version. If replica shard allocations are blocked due to insufficient eligible nodes on the later version, continue upgrading your nodes to resolve the preceding errors. |
shainaraskas
approved these changes
Aug 21, 2026
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Stef Nestor <26751266+stefnestor@users.noreply.github.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.
Summary
👋 Adding back in a variation of an earlier sentence that got moved to main upgrade doc (#6396, #5848).
Generative AI disclosure