By popular demand, here's a quick take on MongoDB 4.2.6's transaction system. There are CHARTS, there are GRAPHS, okay it's mostly CHARTS OF GRAPHS but they're really cool anomalies and I hope you enjoy them. http://jepsen.io/analyses/mongodb-4.2.6 …
-
-
allowed to lose data & read uncommitted, possibly impossible states by default, because why would you *not* want that behavior from something called a transaction. This was already documented, but I found it surprising! (2/2)
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Also the `snapshot` read concern doesn't actually give you snapshot reads unless you commit with write concern `majority`, and apparently this is... by design? Even for read-only transactions? I have questions!
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I thought they fixed their major issues a couple of years ago.
-
MongoDB has certainly made significant improvements over the years! The transaction API didn't exist a couple years ago, though--this is all new territory for Jepsen.
End of conversation
New conversation -
-
-
Spooky indeed.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
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.
