4 ms·
The below is not a seven year old meme: Even at the strongest levels of read and write concern, MongoDB 4.2.6 failed to preserve snapshot isolation. Instead, J
by oxfordmale 6y ago
The below is not a seven year old meme:
Even at the strongest levels of read and write concern, MongoDB 4.2.6 failed to preserve snapshot isolation. Instead, Jepsen observed read skew, cyclic information flow, duplicate writes, and internal consistency violations. Weak defaults meant that transactions could lose writes and allow dirty reads, even downgrading requested safety levels at the database and collection level.
- asya999 6y agoThat was a result of a bug https://jira.mongodb.org/browse/SERVER-48307 https://jira.mongodb.org/browse/SERVER-48307 in the retry mechanism when commitTransaction failed to return a response and has been fixed in 4.2.8. Not all databases have memes, I have a high degree of certainty all of them have bugs.
- fortran77 6y agoI find MongoDB to be a very reliable database as long as I build my apps to tolerate losing data.
- jd_mongodb 6y agoIf you have ever lost data running MongoDB (whether you are a paying customer or not) we want to hear about that and fix it. We treat any instance of data loss as a high priority bug.