honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Clarify stale shard issue on Resiliency page

This commit is contained in:
Jason Tedor 2015-11-13 12:40:35 -05:00
parent 42470c252c
commit a846a257c5
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/resiliency/index.asciidoc
View File

@ -207,9 +207,10 @@ While we are working on a longer term solution ({GIT}9176[#9176]), we introduced
[float] [float]
=== Do not allow stale shards to automatically be promoted to primary (STATUS: ONGOING) === Do not allow stale shards to automatically be promoted to primary (STATUS: ONGOING)
In some scenarios, a succession of multiple isolated nodes can cause a stale replica shard to be promoted to primary In some scenarios, after loss of all valid copies, a stale replica shard can be assigned as a primary. This can lead to
leading to a loss of acknowledged indexing operations. Work is underway ({GIT}14671[#14671]) to prevent the automatic a loss of acknowledged writes if the valid copies are not lost but are rather temporarily isolated. Work is underway
promotion of a stale primary and only allow such promotion to occur when a system operator manually intervenes. ({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 == Completed