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:https://www.mongodb.com/jepsen
-
-
Show this thread
-
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. http://www.vldb.org/pvldb/vol12/p2071-schultz.pdf …pic.twitter.com/SVmiygpkwm
Show this thread -
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 (1/2)
Show this thread -
defaults, then of *course* you should educate people about it! Or, you know, choose safer defaults. That's an option! (2/2)
Show this thread
End of conversation
New conversation -
-
-
here's the commit that introduced the patch that was just removed as part of the ticket you linked to. Kinda concerned by the lack of comments in either commit message or in the code itselfhttps://github.com/mongodb/mongo/commit/adc119c397aecfc956e90d21b04aa5be196249c0#diff-b427932483199a010482241eb16e8937R760 …
-
also I cannot imagine how difficult it must be to write and maintain a test suite for database replication behavior, in *Javascript*
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.