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

[DOCS] Fix 404s (#62918) (#63013) 

Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>

Co-authored-by: Guido Lena Cota <guido.lenacota@kreuzwerker.de>
This commit is contained in:
James Rodewig 2020-09-29 10:37:26 -04:00 committed by GitHub
parent 42437e4b29
commit 26f98f3a74
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/plugins/integrations.asciidoc
View File

@ -101,7 +101,7 @@ releases 2.0 and later do not support rivers.
[discrete]
==== Supported by the community:
* https://camel.apache.org/elasticsearch.html[Apache Camel Integration]:
* https://camel.apache.org/components/2.x/elasticsearch-component.html[Apache Camel Integration]:
An Apache camel component to integrate Elasticsearch
* https://metacpan.org/pod/Catmandu::Store::ElasticSearch[Catmandu]:

4
docs/resiliency/index.asciidoc
View File

@ -227,8 +227,8 @@ fixes to the model and validated that the fixed design behaved as expected.
We have increased our test coverage to include scenarios tested by Jepsen that demonstrate loss of acknowledged writes, as described in
the Elasticsearch related blogs. We make heavy use of randomization to expand on the scenarios that can be tested and to introduce
new error conditions.
You can follow the work on the master branch of the
https://github.com/elastic/elasticsearch/blob/master/core/src/test/java/org/elasticsearch/discovery/DiscoveryWithServiceDisruptionsIT.java[`DiscoveryWithServiceDisruptionsIT` class],
You can view these changes on the `5.0` branch of the
https://github.com/elastic/elasticsearch/blob/5.0/core/src/test/java/org/elasticsearch/discovery/DiscoveryWithServiceDisruptionsIT.java[`DiscoveryWithServiceDisruptionsIT` class],
where the `testAckedIndexing` test was specifically added to check that we don't lose acknowledged writes in various failure scenarios.