Skip to content

Update troubleshooting-upgrades.md - #8051

Merged
stefnestor merged 2 commits into
mainfrom
stefnestor-patch-4
Aug 21, 2026
Merged

Update troubleshooting-upgrades.md#8051
stefnestor merged 2 commits into
mainfrom
stefnestor-patch-4

Conversation

@stefnestor

Copy link
Copy Markdown
Member

Summary

👋 Adding back in a variation of an earlier sentence that got moved to main upgrade doc (#6396, #5848).

During a rolling upgrade, primary shards assigned to a node running the new version cannot have their replicas assigned to a node with the old version. The new version might have a different data format that is not understood by the old version.

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No

👋 Per [private link](elastic/sdh-elasticsearch#10214 (comment)) adding back in an earlier sentence that got moved to main upgrade doc.
@stefnestor
stefnestor requested a review from a team as a code owner August 21, 2026 22:22
@stefnestor stefnestor added the enhancement New feature or request label Aug 21, 2026
@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check 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.

@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown
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.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Comment thread troubleshoot/elasticsearch/troubleshooting-upgrades.md Outdated
* `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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"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.

Comment thread troubleshoot/elasticsearch/troubleshooting-upgrades.md Outdated
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>
@stefnestor
stefnestor enabled auto-merge (squash) August 21, 2026 22:44
@stefnestor
stefnestor merged commit 1bd60d5 into main Aug 21, 2026
8 of 9 checks passed
@stefnestor
stefnestor deleted the stefnestor-patch-4 branch August 21, 2026 22:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants