Hey @CloudNativeFdn: It would be hugely helpful to practitioners for the @linuxfoundation to engage (i.e., pay) @aphyr to do Jepsen (re-)runs on the projects in your purview (e.g., #etcd, #TiKV). Any chance of this?
-
-
Replying to @bcantrill @CloudNativeFdn and
I sincerely wish someone would pay
@aphyr for rerunning it on Cassandra as well.1 reply 0 retweets 2 likes -
Replying to @jaseemabid @bcantrill and
The work
@cscotta & co have been putting into Cassandra fault testing covers much more than my original Jepsen tests.1 reply 3 retweets 16 likes -
Replying to @aphyr @bcantrill and
Awesome! Id love to read anything related to it. We run a lot of critical Cassandra workloads.
1 reply 0 retweets 2 likes -
Replying to @jaseemabid @aphyr and
For sure! Here’s an overview of some of the methodologies we are employing: http://cassandra.apache.org/blog/2018/08/21/testing_apache_cassandra.html … And a deep dive on property-based testing: http://cassandra.apache.org/blog/2018/10/17/finding_bugs_with_property_based_testing.html …
1 reply 4 retweets 15 likes
About ~30 of the issues identified and resolved in 3.0.17+ and 3.11.3+ were found via these methodologies. The community’s investment is making Cassandra a better, safer database. DM if you’d like to talk more; would love to learn about what you’re building on C*!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.