tl;dr: MongoDB 4.2.6's transactions aren't full ACID, or even snapshot isolated. We found read skew, cyclic information flow, and internal inconsistencies, including transactions which could read their own writes from the future. Ooooh, spooooky! Also transactions are (1/2)
-
-
Show this thread
-
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 thread
End of conversation
New conversation -
-
-
FYI, found out if I try to open analysis .zip file I got the message complaining about certificate issue for http://jepsen.io.s3.amazonaws.com pic.twitter.com/iTorNyXcdS
-
Oh, yeah, this is an issue with amazon's *-certificates. Guess I gotta downgrade to http and rename buckets going forward?
- 3 more replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thank you Kyle! A very good detailed article.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Outstanding. Maybe there can be a sequel in a year or so and we'll have a whole MongoDb Trilogy. Sort of like the Star Wars prequels, funny if you're not overly involved.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Está claro, la necesidad real transaccional multicolección de los clientes mongodb era de un 10% si no recuerdo mal. Poner por poner
@transactional es un error , ya te lo dije ayer
- 2 more replies
New conversation -
-
.. and I'm worried about optimistic cache collision resolution
Great article @jepsen_io
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.
