Re:Elasticsearch node crashes can cause data loss
by sitkack on Saturday May 02, 2015 @08:54AM
(#9476876)
Fsync should always be on by default. Require the user to turn it off. I'd even argue that `fsync` itself is broken and that semantics should be inverted.
Re:Elasticsearch node crashes can cause data loss
by eternalban on Saturday May 02, 2015 @10:08AM
(#9477083)
What about pervasive virtualization? The issue here is not really fsync. A fault-tolerant in-memory cluster should not lose data.
Re:Elasticsearch node crashes can cause data loss
by sitkack on Saturday May 02, 2015 @12:39PM
(#9477621)
Writes should be durable by whatever means the platform deems durable. Durable should be the default. It should take work to have non-durable io.
Re:Elasticsearch node crashes can cause data loss
by andrewdanks on Saturday May 02, 2015 @11:14AM
(#9477351)
> always know your DB
True, but Elasticsearch is not intended to be a permanent datastore.
> by not fsync'ing each operation (though one can configure ES to do so).
It may not be default, but we've seen, again and again, how people are influenced by what they read about a database (e.g. MongoDB).
The lesson by now should be: always know your DB.