4 ms·
This is a powerful validation for etcd and its status as a mission critical backend. You don't see a lot of positive Jespen results these days!
by candiddevmike 7y ago
This is a powerful validation for etcd and its status as a mission critical backend. You don't see a lot of positive Jespen results these days!
- shaklee3 7y agoI didn't think it was too positive. He found some documentation bugs, as well as what seems like really bad locking bugs.
- nl 7y agoHave you seen Jepsen reports before? Silent data loss isn't uncommon. https://aphyr.com/posts/284-call-me-maybe-mongodb https://aphyr.com/posts/284-call-me-maybe-mongodb ("Mostly, it just throws those writes away entirely: no rollback files, no nothing. I don’t really know why.") https://aphyr.com/posts/317-call-me-maybe-elasticsearch https://aphyr.com/posts/317-call-me-maybe-elasticsearch ("When the cluster comes back together, one primary blithely overwrites the other’s state.") etc etc
- senderista 7y agoIt is not possible to implement distributed locking correctly in the general case. Fencing tokens only work if your data store supports RMW operations, in which case you could just implement locking inside the data store itself.