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

Merge pull request #14681 from jasontedor/stale-shard-resiliency 

Add stale shard issue to Resiliency page
This commit is contained in:
Jason Tedor 2015-11-11 10:33:53 -05:00
parent beffc88700 7b16e82df4
commit 0f338491c6
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/resiliency/index.asciidoc
View File

@ -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) 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)
In some scenarios, a succession of multiple isolated nodes can cause a stale replica shard to be promoted to primary
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 == Completed
[float] [float]