News for hackers. Stuff that matters.

A comment on MongoDB 3.4.0-rc3. Parent comment

Re:MongoDB 3.4.0-rc3 by siscia on Tuesday February 07, 2017 @12:11PM (#13590789)
> In addition, we show that the new v1 replication protocol has multiple bugs, allowing data loss in all versions up to MongoDB 3.2.11 and 3.4.0-rc4. While the v0 protocol remains broken, patches for v1 are available in MongoDB 3.2.12 and 3.4.0, and now pass the expanded Jepsen test suite.

Wait, it is me not understanding what the abstract is trying to say?

[ Parent | on HN ]
Re:MongoDB 3.4.0-rc3 by ealexhudson on Tuesday February 07, 2017 @12:15PM (#13590809)
It's saying it was fixed in the final 3.4.0 release (or, maybe, that there's at least a patch available) for the v1 protocol, but that the v0 protocol is unfixable - so, 3.4.0 + V1 protocol and it's solid.

Giving aphyr some money to do this makes me think much more of Mongo now; I wouldn't previously have considered it for serious use but this is an excellent demonstration of intent.

[ Parent | on HN ]
Re:MongoDB 3.4.0-rc3 by wslh on Tuesday February 07, 2017 @12:15PM (#13590808)
I can only think that the article was a bit late and the new MongoDB version has the last word. Beyond this, the article is extremely valuable and it is mandatory to upgrade your MongoDB.
[ Parent | on HN ]
Re:MongoDB 3.4.0-rc3 by aphyr on Tuesday February 07, 2017 @12:23PM (#13590888)
This analysis was a collaboration with MongoDB over the past three months. MongoDB was able to fix these issues in 3.4.0 because I found them in rc3 and rc4.
[ Parent | on HN ]
Re:MongoDB 3.4.0-rc3 by wslh on Tuesday February 07, 2017 @12:32PM (#13590967)
Sorry, my fault.
[ Parent | on HN ]