These jepsen tests cover elasticsearch 1.5, a large number of issues have been progressively fixed. We're now at ES 6
Note that 3 and 4 were skipped; ES 2 was followed by ES 6.
ES 2 was followed by ES 5.
The results for ElasticSearch are from 2015, curious to see how relevant they are now especially given that the team has been working on addressing these issues in the interim.
Re:Elastic files for an IPO
by tschellenbach on Wednesday September 05, 2018 @05:21PM
(#17922023)
Also elastic back then was used as a place where you copy your data, not your main data store. (Their positioning changed later) MongoDB was supposed to be used for your primary data store.
Those Jepsen are not that useful, I can point to you Postgres issues where it would corrupt the DB, does it means you shoudn't use Postgres?
https://aphyr.com/posts/317-jepsen-elasticsearch
https://aphyr.com/posts/323-jepsen-elasticsearch-1-5-0
Though, all those issues have been fixed for both MongoDB and Elasticsearch so it's not necessarily fair to judge them based off past performance.
https://www.elastic.co/guide/en/elasticsearch/resiliency/cur...
https://www.mongodb.com/mongodb-3.4-passes-jepsen-test