From 3267c2a2bfc44e9e8d6abb0c10a8c77da22fa1ec Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Thu, 2 Oct 2014 21:08:32 +0200 Subject: [PATCH] Docs: Updated the resiliency docs to point to the DiscoveryWithServiceDisruptions class --- docs/resiliency/index.asciidoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/resiliency/index.asciidoc b/docs/resiliency/index.asciidoc index ee64c965559..16361d9b595 100644 --- a/docs/resiliency/index.asciidoc +++ b/docs/resiliency/index.asciidoc @@ -105,9 +105,7 @@ Today, when a node holding a primary shard receives an index request, it checks [float] === Jepsen Test Failures (STATUS: ONGOING) -As has been noted, Elasticsearch fails with a split-brain condition (as described in issue {GIT}2488[#2488]) in some corner cases as revealed by Jepsen testing. You can check on the progress we are making on this issue in the section above or by checking in https://github.com/dakrone/elasticsearch/compare/feature/zen/add-jepsen-test[directly on GitHub]. It is possible that Jepsen testing will highlight some other potential issues, and we are continuing our investigation. - -Our current plan is to run Jepsen against the recent changes in master, and make sure that each Jepsen test has a corresponding test in our new transport test infrastructure, with a documented PASS/FAIL status against it. +We have increased our test coverage to include scenarios tested by Jepsen. 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/elasticsearch/elasticsearch/blob/master/src/test/java/org/elasticsearch/discovery/DiscoveryWithServiceDisruptions.java[`DiscoveryWithServiceDisruptions` class], where we will add more tests as time progresses. [float] === Document guarantees and handling of failure (STATUS: ONGOING)