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 …
-
-
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 -
-
-
If I got no concerns, I got no worries!pic.twitter.com/OZfRmbo2hP
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That's interesting. With Atlas the default connection string you pull for a cluster does have w=majority but nothing specified for read.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.