-
The rest of my notes from the
#Jepsen workshop with@aphyr Including explanations about concurrency with cats
!pic.twitter.com/dDEBqJipyp
-
Learning about
#Jepsen fundamentals during our#Jepsen workshop with@aphyrpic.twitter.com/FXLEMK87rc
-
-
Most systems fail
#Jepsen test.@VoltDB passed in v6.4. Not all vendors fix what#Jepsen finds, VoltDB does. pic.twitter.com/fX695UocVA
-
In this
#Jepsen analysis, we explore three safety bugs in@YugaByte DB: a distributed, multi-model database which combines sharded instances of Raft with leader leases, hybrid logical clocks, and a custom 2PC cross-shard transactional protocol. https://jepsen.io/analyses/yugabyte-db-1.1.9 …Prikaži ovu nit -
In the latest
#Jepsen analysis, we worked with@pingcap to test TiDB 2.1.7 through 3.0.0-rc.2. Due to 2 transaction retry mechanisms, TiDB exhibited constant snapshot isolation anomalies under normal conditions. This and other bugs are fixed in 3.0.0-rc.2: https://jepsen.io/analyses/tidb-2.1.7 … -
Integrating
@aphyr’s#Jepsen into our CI presented challenges, now protects us from regressions in linearizability: https://engineering.mongodb.com pic.twitter.com/jUlA7eq3sW
-
Starting out our
#Jepsen workshop with@aphyr with an intro to#Clojure!
pic.twitter.com/Cl3YlYOkdC
-
In this
#Jepsen analysis, we look at Hazelcast: an in-memory data grid with a habit of forgetting. https://jepsen.io/analyses/hazelcast-3-8-3 …Prikaži ovu nit -
How can someone be so bad at their job?
#Jepsen -
New
#Jepsen analysis: the Tendermint blockchain system for byzantine fault tolerant replication of state machines: https://jepsen.io/analyses/tendermint-0-10-2 …Prikaži ovu nit -
New
#Jepsen report! We worked with@YugaByte to evaluate YugaByte DB 1.3.1's beta support for serializable SQL transactions. We found 2 safety bugs including anti-dependency cycles (now fixed), and availability issues like a slow leak in backend processes. https://jepsen.io/analyses/yugabyte-db-1.3.1 …Prikaži ovu nit -
New
#Jepsen analysis: reviewing and expanding@cockroachdb's tests. We found & fixed serializability violations! https://jepsen.io/analyses/cockroachdb-beta-20161013 … -
@aphyr Thanks for#Jepsen! now that it passed, we'll contribute enhancements to it. http://www.scylladb.com/2016/02/11/jepsen-testing/ … -
I've been experimenting with
#Jepsen to check for application correctness, here's a writeup of where I got to & how: https://caligin.github.io/2017/08/29/experimenting-with-jepsen.html …Prikaži ovu nit -
In the latest
#Jepsen analysis, we return to@aerospikedb 3.99.0.3, checking their next-generation consensus system scheduled to be released in 4.0. We confirm data loss due to process crashes and 27+ second pauses, and found a subtle bug in proxied nacks. https://jepsen.io/analyses/aerospike-3-99-0-3 …Prikaži ovu nit -
RethinkDB 2.2.3: A rare case of split-brain after cluster reconfiguration
#jepsen https://aphyr.com/posts/330-jepsen-rethinkdb-2-2-3-reconfiguration … -
Testing the
#Hazelcast#CP Subsystem with#Jepsen https://hazelcast.com/blog/testing-the-cp-subsystem-with-jepsen/ … -
Thrilled to announce that
@YugaByte DB has passed official#Jepsen testing! It was a pleasure to collaborate with@aphyr on this; and super proud of the engineering team for reaching this milestone so quickly-- no easy task for a distributed database!https://twitter.com/jepsen_io/status/1110575993297739776 … -
Interesting insights on how
@DataStax uses#Jepsen for#Cassandra testing: http://www.datastax.com/dev/blog/testing-apache-cassandra-with-jepsen …
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.



