3 ms·
No, not for writing. It's never safe. It will eventually eat your data. But for reading it's fine. So by all means, you can populate from a main data store tha
by swsieber 10y ago
No, not for writing. It's never safe. It will eventually eat your data.
But for reading it's fine. So by all means, you can populate from a main data store that you never otherwise touch.
Then again, if you're running just a single instance on really small data... What could go wrong?
Edit: Again, small stuff, locally, it's probably fine. But ElasticSearch wasn't really built to be a primary data store.
Sources:
https://aphyr.com/posts/332-jepsen-crate-0-54-9-version-divergence https://aphyr.com/posts/332-jepsen-crate-0-54-9-version-dive... (This has links to other good sources, right in the beginning).
https://news.ycombinator.com/item?id=11325316 https://news.ycombinator.com/item?id=11325316
https://news.ycombinator.com/item?id=11362069 https://news.ycombinator.com/item?id=11362069
- bryanrasmussen 10y agoyeah, I agree if your requirements is data consistency then not Elasticsearch, however I think from the Jepsen tests I don't think there has been any NoSQL db that performs really good on that? ( I seem to remember there was one that did bad on the first test but improved a lot with the second - SOLR, CouchDB?)
- earleybird 10y agoyou're thinking of RethinkDB https://aphyr.com/posts/329-jepsen-rethinkdb-2-1-5 https://aphyr.com/posts/329-jepsen-rethinkdb-2-1-5
- bryanrasmussen 10y agoThanks! I knew someone would have either a better memory than me or the willingness to actually go to http://jepsen.io/analyses.html http://jepsen.io/analyses.html and figure out which one it was! And now that I went I see both the ones I thought it might be haven't even ever been done! I need to run a Jepsen test on my brain.