Re:ScyllaDB: Drop-in replacement for Cassandra that claims t...
by cbsmith on Wednesday September 23, 2015 @02:30AM
(#10263597)
Except that problem has been largely addressed now.
Re:ScyllaDB: Drop-in replacement for Cassandra that claims t...
by saurik on Wednesday September 23, 2015 @02:42AM
(#10263636)
I really really really want to see Aphyr attack the patched version to see if he thinks the fix actually worked.
Re:ScyllaDB: Drop-in replacement for Cassandra that claims t...
by gegtik on Wednesday September 23, 2015 @10:38AM
(#10265232)
Datastax is presenting on the topic at their Summit on thursday
http://cassandrasummit-datastax.com/agenda/testing-cassandra...
Re:ScyllaDB: Drop-in replacement for Cassandra that claims t...
by sargun on Wednesday September 23, 2015 @03:40AM
(#10263781)
How so? The fundamental flaw was using timestamps.
Re:ScyllaDB: Drop-in replacement for Cassandra that claims t...
by acconsta on Wednesday September 23, 2015 @02:46AM
(#10263643)
Right, I should add that it was two years ago. My point is that the age of a project has nothing to do with the correctness of its Paxos implementation.
Re:ScyllaDB: Drop-in replacement for Cassandra that claims t...
by cbsmith on Wednesday September 23, 2015 @12:10PM
(#10265905)
Jepsen's finding wasn't that there was a bug in Paxos. It was in how it handled conflicts.
Re:ScyllaDB: Drop-in replacement for Cassandra that claims t...
by acconsta on Wednesday September 23, 2015 @01:48PM
(#10266633)
"So you confer with DataStax for a while, and they manage to reproduce and fix the bug: #6029 (Lightweight transactions race render primary key useless), and #5985 (Paxos replay of in progress update is incorrect). You start building patched versions of Cassandra."
"Cassandra lightweight transactions are not even close to correct. Depending on throughput, they may drop anywhere from 1-5% of acknowledged writes–and this doesn’t even require a network partition to demonstrate. It’s just a broken implementation of Paxos. In addition to the deadlock bug, these Jepsen tests revealed #6012 (Cassandra may accept multiple proposals for a single Paxos round) and #6013 (unnecessarily high false negative probabilities)."
That's four bugs independent of the conflict resolution issue.
https://aphyr.com/posts/294-call-me-maybe-cassandra/