Skip to content

Add stale shard issue to Resiliency page #14681

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 11, 2015
Merged

Add stale shard issue to Resiliency page #14681

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/resiliency/index.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,6 +204,13 @@ Commonly used filters are cached in Elasticsearch. That cache is limited in size

While we are working on a longer term solution ({GIT}9176[#9176]), we introduced a minimum weight of 1k for each cache entry. This puts an effective limit on the number of entries in the cache. See {GIT}8304[#8304] (STATUS: DONE, fixed in v1.4.0)

[float]
=== Do not allow stale shards to automatically be promoted to primary (STATUS: ONGOING)
Copy link
Contributor

Choose a reason for hiding this comment

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

"Do not allow stale shards to automatically be promoted to primary if all other copies are lost" ?


In some scenarios, a succession of multiple isolated nodes can cause a stale replica shard to be promoted to primary
Copy link
Contributor

Choose a reason for hiding this comment

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

How about "In some scenarios, after loss of all valid copies, a stale replica shard can be assigned as a primary. This can lead to a loss of acknowledged writes, if the valid copies are not lost but are rather temporally isolated by a network partition"?

leading to a loss of acknowledged indexing operations. Work is underway ({GIT}14671[#14671]) to prevent the automatic
promotion of a stale primary and only allow such promotion to occur when a system operator manually intervenes.

== Completed

[float]
Expand Down