I've read a few things about lost writes if a partition is underway or write loads pass certain thresholds (https://www.google.com.au/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=elasticsearch%20lost%20writes). It's obviously not suitable as a primary data store if this is the case.
On Tuesday, June 7, 2016 at 11:41:47 PM UTC+10, Jochen Schalanda wrote: > > Hi Jona, > > a well maintained Elasticsearch cluster is a good enough and resilient > data store. Are there any specific reasons leading to your conclusion that > this was a problem? > > Cheers, > Jochen > > On Tuesday, 7 June 2016 14:40:47 UTC+2, Jona Thon wrote: >> >> Am I wrong in understanding that Elasticsearch, while being a great >> search/index system, isn't a particularly dependable datastore? I ask >> because I'm considering making GreyLog my primary store for log data and >> the reports of lost writes worry me. I know the Elassandra project has >> built a Cassandra backend for ES to help address this risk. . Has there >> ever been discussion on this topic? >> > -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/6ebfc396-e6d2-4b58-ae2c-e410e7ebd9b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
