Re:Setting Up a Fast, Comprehensive Search Routine with Post...
by aisofteng on Sunday July 29, 2018 @10:45PM
(#17641699)
After reading the links you gave, I’d like to clarify that I meant that edge cases that can cause data loss are not common enough, in my experience, for one to be forced to treat ElasticSearch as an unreliable data store. Anecdotally, I’ve never seen it happen. You’re right, maybe I’m lucky; I would like to see a case study of some project where these issues were significant enough to treat ElasticSearch as an unreliable data store.
Read the jepsen tests (old but show core problems that aren't fixed):
https://aphyr.com/posts/317-call-me-maybe-elasticsearch
https://aphyr.com/posts/323-call-me-maybe-elasticsearch-1-5-...
Or just search for ES data loss:
https://news.ycombinator.com/item?id=9475620
https://stackoverflow.com/questions/29841348/how-reliable-is...
And if that's not enough, here's the official page listing several "ongoing" fixes for major durability issues:
https://www.elastic.co/guide/en/elasticsearch/resiliency/cur...