Skip to content

Conversation

@georgewallace
Copy link
Contributor

No description provided.

: An isolated primary can expose writes that will not be acknowledged. This is caused by the fact that an isolated primary will only realize that it is isolated once it sends requests to its replicas or when reaching out to the master. At that point the operation is already indexed into the primary and can be read by a concurrent read. Elasticsearch mitigates this risk by pinging the master every second (by default) and rejecting indexing operations if no master is known.


## The Tip of the Iceberg [_the_tip_of_the_iceberg]
Copy link
Contributor

Choose a reason for hiding this comment

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

Very minor but jumped out at me. We use sentence case in our titles in general

Suggested change
## The Tip of the Iceberg [_the_tip_of_the_iceberg]
## The tip of the iceberg [_the_tip_of_the_iceberg]

Copy link
Contributor

@lcawl lcawl left a comment

Choose a reason for hiding this comment

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

I've added some extra suggestions but IMO once the links are fixed it's good to go

georgewallace and others added 2 commits March 18, 2025 16:27
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
@georgewallace georgewallace merged commit ea0ac43 into elastic:main Mar 18, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants