[Internal]: Describe the Elastic Cloud tiebreaker on the voting-only and resilience pages
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Read the voting-only section and the two-zone tiebreaker section linked in the issue, then locate their source files in the documentation repository. Add an admonition to both pages explaining the Elastic Cloud Hosted and Elastic Cloud Enterprise tiebreaker instance and that two-zone deployments include one automatically. The documentation team will create the first draft; done means both pages communicate this distinction clearly.
Written by the indexing model from the issue text.
Description
Description
The voting-only section says a voting-only node can serve as a tiebreaker in elections. The two-zone tiebreaker section already calls that node a dedicated tiebreaker. That page focuses on self-managed clusters and points Elastic Cloud Hosted and Elastic Cloud Enterprise readers elsewhere.
On a two-zone deployment, Elastic Cloud Hosted and Elastic Cloud Enterprise add one tiebreaker instance automatically. The create screen says:
We automatically include a single tiebreaker node for your deployment to help prevent a split-brain situation during master elections.
Learn more on that note lands on the resilience page.
We need an admonition on both pages. In Elastic Cloud Hosted and Elastic Cloud Enterprise, this node is a tiebreaker instance, and a two-zone deployment adds one automatically.
The documentation team writes the first draft.
Resources
- Voting-only section: https://www.elastic.co/docs/deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles#voting-only-node:~:text=A%20voting-only%20master-eligible%20node%20is%20a%20node%20that%20participates%20in%20master%20elections
- Two-zone tiebreaker section: https://www.elastic.co/docs/deploy-manage/production-guidance/availability-and-resilience/resilience-in-larger-clusters#two-zone-clusters-with-a-tiebreaker:~:text=also%20known%20as%20a%20dedicated%20tiebreaker
- Specialization channel thread: https://elastic.slack.com/archives/C045SG0FRGW/p1795056203998019
- Support tracking: https://github.com/elastic/support-tech-lead/issues/2032
Which deployment methods does this change impact?
Elastic On-Prem and Cloud (all)
Feature differences
Elastic Cloud Hosted and Elastic Cloud Enterprise add the tiebreaker instance when the deployment has two zones. Self-managed clusters and Elastic Cloud on Kubernetes configure a voting-only node themselves. Serverless does not use this instance.
What Elastic Stack release is this request related to?
N/A
Serverless release
No response
Collaboration model
The documentation team will create the first draft
Point of contact.
Main contact: @kunisen
Stakeholders:
Assisted by Cursor 🤖
- Dominant language
- No language data
- Stars
- 50
- Forks
- 269
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 241
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from elastic/docs-content
-
Feature: Security General Team:SKI triaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elastic/docs-content#9520 · 4 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
source:web Team:SKI triaged
Difficulty 1/5 Under an hour Newbie friendliness 85/100
elastic/docs-content#9508 · 1 comment · 1 reaction ·
Maintainers usually reply within 2 days
-
Team:SKI triaged
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/docs-content#9493 · 1 comment · 1 reaction ·
Maintainers usually reply within 2 days
-
Preview generated workflows as a graph or YAML in Agent ChatPossibly taken @nastasha-solomon claimed this 1 day ago. OpenFeature: Workflows Team:SKI triaged
Difficulty 1/5 Under an hour Newbie friendliness 85/100
elastic/docs-content#9463 · 1 comment · 1 reaction · 1 assignee ·
Maintainers usually reply within 2 days
-
[Alerting V2] Get ES|QL help and recommended queries in the rule query sandboxPossibly taken @nastasha-solomon claimed this 3 days ago. Openalerting-v2 Team:SKI triaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
elastic/docs-content#9428 · 1 comment · 1 reaction · 1 assignee ·
Maintainers usually reply within 2 days
All issues in elastic/docs-content
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 89/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Area/Connector module/solace Priority/Low Type/Docs
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
ballerina-platform/ballerina-library#9850 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
gke-labs/kube-agents#6620 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EveryInc/compound-engineering-plugin#2091 ·
Maintainers usually reply within 1 day