5 ms·
Suggested reading -- the link. > 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 agai
by klapinat0r 11y ago
Suggested reading -- the link.
> 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.
- sitkack 11y agoFsync 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.
- eternalban 11y agoWhat about pervasive virtualization? The issue here is not really fsync. A fault-tolerant in-memory cluster should not lose data.
- sitkack 11y agoWrites should be durable by whatever means the platform deems durable. Durable should be the default. It should take work to have non-durable io.
- andrewdanks 11y ago> always know your DB True, but Elasticsearch is not intended to be a permanent datastore.