[Internal]: Describe the Elastic Cloud tiebreaker on the voting-only and resilience pages

Open Beginner friendly
#9,532 1 comment 1 reaction 0 assignees View on GitHub

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

Team:Admin triaged
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
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/docs-content

All issues in elastic/docs-content

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.