3 ms·
Please note that I replied to this blog post, when it was published. You may be interested in reading the counter arguments. The author of the original post ack
by antirez 3y ago
Please note that I replied to this blog post, when it was published. You may be interested in reading the counter arguments. The author of the original post acknowledged that at least one of his claim was wrong, but I don't know if they modified the post later. Anyway we gained some time perspective, too: Redlock was massively used in the last 10 years, and I have never heard of its properties failing in the practice: that is, no incidents so far.
http://antirez.com/news/101 http://antirez.com/news/101
- eternalban 3y agoDiscussed earlier: https://news.ycombinator.com/item?id=11065933 https://news.ycombinator.com/item?id=11065933 Someone mentioned "the saddest moment" in there in response to the back and forth comment: https://www.usenix.org/system/files/login-logout_1305_mickens.pdf https://www.usenix.org/system/files/login-logout_1305_micken... (hope all is well!)
- rubiquity 3y ago> Redlock was massively used in the last 10 years, and I have never heard of its properties failing in the practice: that is, no incidents so far. I enjoyed these posts between yourself and Martin. Don’t be too confident though. Data races almost always go unnoticed.
- antirez 3y agoThank you. I agree about races going unnoticed. And indeed my post tryed to address why the failure modes outlined in the original post are not possible (but for the monothonic timer issue, but this was fixed in Redis at some point).