MongoDB found a bug in the retry mechanism which they think is responsible for the issues we found in 4.2.6--a fix is scheduled for 4.2.8!

jira.mongodb.org/browse/SERVER

MongoDB rewrote their Jepsen page, but it still goes to great lengths to avoid talking about write loss or aborted reads, both of which are the default behavior:

mongodb.com/jepsen

I keep thinking about their VLDB paper which says ~80% of writes to MongoDB's hosted service don't set a write concern, and 99.6% of reads don't set a read concern. vldb.org/pvldb/vol12/p2071-sch

If users are really aware of, and OK with, with write loss by default (presumably because the probability of failure is small or the impact is low) then it should be fine to talk about it. If users *aren't* aware of this behavior, but most are subject to it by accepting defaults, then of *course* you should educate people about it!

Or, you know, choose safer defaults. That's an option!

Follow

I called this out in the report as well, but the write concern documentation still doesn't say anything about rollbacks/write loss: docs.mongodb.com/manual/refere

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Jepsen

A single-user Mastodon instance for Jepsen announcements & discussion.