I think you mean Jepsen? It's a slight exaggeration to say that RethinkDB aced it -- but they did very well[1] and (more importantly to me, honestly) Jepsen was used to find a subtle and nasty issue that was subsequently fixed.[2]
I've been having a lot of trouble with Jenkins at work today. So when I though Jepsen, I wrote Jenkins.
Still feel they aced it. No one passes Jepsen on their first try. But RethinkDB is the first to immediately fix the issue.
I wouldn't go as far as to call it a nasty issue. It would only happen if you got node failures while reconfiguring your cluster. And reconfiguring the cluster must be initiated by the admin and it's something that happens very often.
Still feel they aced it. No one passes Jepsen on their first try. But RethinkDB is the first to immediately fix the issue.
I wouldn't go as far as to call it a nasty issue. It would only happen if you got node failures while reconfiguring your cluster. And reconfiguring the cluster must be initiated by the admin and it's something that happens very often.