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! https://jira.mongodb.org/browse/SERVER-48307 …
-
Show this thread
-
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
1 reply 14 retweets 14 likesShow 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
3 replies 1 retweet 5 likesShow 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)
3 replies 1 retweet 2 likesShow this thread
defaults, then of *course* you should educate people about it! Or, you know, choose safer defaults. That's an option! (2/2)
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.