Add master not discovered error for searchability#6536
Merged
stefnestor merged 4 commits intoMay 28, 2026
Conversation
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
✅ Vale Linting ResultsNo 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. |
2 tasks
Contributor
There was a problem hiding this comment.
Docs review summary
Focus areas
- Style and clarity: One future-tense issue on the new sentence at line 85 ("will log" → "logs"). The new API error block and paragraph additions read clearly.
- Jargon:
MasterNotDiscoveredExceptionandmaster_not_discovered_exceptionare used correctly in inline code/code blocks; the link to master-eligible nodes provides helpful context. - Frontmatter and applies_to: Pre-existing; no changes introduced by this PR.
- Content type fit: Troubleshooting page. The new content (error payload example + log identifiers) fits the resolution pattern well.
- Parent issue satisfaction: No linked issue. The PR's stated goal — making the master-not-discovered error searchable — is satisfied by the additions.
Notes
- Vale found no findings for the eligible files. One manual style finding (future tense) is noted above.
Generated by Docs review agent for issue #6536 · ● 269.8K
Member
Author
|
Cheers, @yetanothertw! Ready again 🙏 . FWIW for grammar-not-technical edits, you're welcome to directly edit not just suggest 🙂 |
stefnestor
added a commit
that referenced
this pull request
Jun 6, 2026
## Summary 👋 Follow-up of #5848 to create separate upgrade troubleshooting page. This assumes but does not breaking rely on errors WIP documenting in - #6534 - #6535 - #6536 - #6537 - elastic/elasticsearch#149765 - elastic/elasticsearch#149768 It will hopefully be less necessary after elastic/kibana#266733 There's various page cross-links/cross-reference between troubleshooting "rolling upgrading Elasticsearch" and the "upgrade assistant" before it, so starting together <details><summary>Non-exhaustive related links</summary> --- - https://support.elastic.co/knowledge/1bbb4cc9 - https://discuss.elastic.co/t/issues-upgrading-elasticsearch-from-8-to-9-due-to-old-7-x-indices-and-restricted-kibana-indices/379133/11 - elastic/kibana#119652 (comment) - https://support.elastic.co/knowledge/3e27188b - https://support.elastic.co/knowledge/56149373 - https://support.elastic.co/knowledge/cb3db1e7 - https://support.elastic.co/knowledge/f3c6ea67 - elastic/elasticsearch#86801 - elastic/kibana#116209 - https://support.elastic.co/knowledge/295e812f - https://support.elastic.co/knowledge/794038f9 - https://support.elastic.co/knowledge/dd79602f - https://support.elastic.co/knowledge/e3d44d38 --- </details> ## Generative AI disclosure 1. Did you use a generative AI (GenAI) tool to assist in creating this contribution? - [ ] Yes - [X] No --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Marci W <333176+marciw@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
👋 howdy! This is one of the most common ES cluster formation/API errors online, but not currently searchable in our docs. So just adds the log & API forms of it. TIA!
Generative AI disclosure