undefined | Better HN

0 pointsnemo44x4y ago0 comments

Well, they did end up making it a pretty good database. They saved the good parts (great clients, dev experience) and got rid of the bad (original storage engine, instability) add and have a legit database. Good on them.

0 pointsnemo44x4y ago0 comments

0 comments

5 comments · 2 top-level

winrid4y ago· 2 in thread

While I want to agree, until this year there were still deadlock issues that could take down whole clusters [0][1].

[0] https://jira.mongodb.org/browse/SERVER-57476

[1] https://jira.mongodb.org/browse/SERVER-56779

tchvil4y ago

A JIRA user is needed to see them I guess. Do you mind to tell what are the issues ?

ddorian434y ago

I could open the issues in icognito mode. 1: Operation may block on prepare conflict while holding oplog slot, stalling replication indefinitely

2: Do not use the collection distributed lock for chunk merges

1 more reply

5e92cb50239222b4y ago· 1 in thread

This was posted not much more than a year ago.

https://jepsen.io/analyses/mongodb-4.2.6

https://news.ycombinator.com/item?id=23290844

https://news.ycombinator.com/item?id=23285249

DonnyV4y ago

Looks like it was a bug and Mongodb fixed it.

j / k navigate · click thread line to collapse