| Pretraživanje | Osvježi |
|
Joy Heron
@iamjoyheron
|
20. ruj 2017. |
|
The rest of my notes from the #Jepsen workshop with @aphyr
Including explanations about concurrency with cats 😸! pic.twitter.com/dDEBqJipyp
|
||
|
||
|
Joy Heron
@iamjoyheron
|
20. ruj 2017. |
|
Learning about #Jepsen fundamentals during our #Jepsen workshop with @aphyr pic.twitter.com/FXLEMK87rc
|
||
|
||
|
Marist Volleyball 🏐
@RedHawkVB
|
17. tra |
|
|
||
|
|
||
|
ann_dalrymple
@ann_dalrymple
|
29. ruj 2016. |
|
Most systems fail #Jepsen test. @VoltDB passed in v6.4. Not all vendors fix what #Jepsen finds, VoltDB does. pic.twitter.com/fX695UocVA
|
||
|
||
|
Jepsen
@jepsen_io
|
26. ožu |
|
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. jepsen.io/analyses/yugab…
|
||
|
|
||
|
Hazelcast
@hazelcast
|
13 h |
|
|
||
|
|
||
|
Zach Chivers
@ZachChivers28
|
26. tra 2016. |
|
How can someone be so bad at their job? #Jepsen
|
||
|
|
||
|
Jepsen
@jepsen_io
|
12. lip |
|
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: jepsen.io/analyses/tidb-…
|
||
|
|
||
|
Scylla
@ScyllaDB
|
11. velj 2016. |
|
@aphyr Thanks for #Jepsen! now that it passed, we'll contribute enhancements to it.
scylladb.com/2016/02/11/jep…
|
||
|
|
||
|
Joy Heron
@iamjoyheron
|
20. ruj 2017. |
|
Starting out our #Jepsen workshop with @aphyr with an intro to #Clojure! 😍 pic.twitter.com/Cl3YlYOkdC
|
||
|
||
|
Yukon Whorenelius
@aphyr
|
5. ruj 2017. |
|
New #Jepsen analysis: the Tendermint blockchain system for byzantine fault tolerant replication of state machines: jepsen.io/analyses/tende…
|
||
|
|
||
|
Jepsen
@jepsen_io
|
5. ruj |
|
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. jepsen.io/analyses/yugab…
|
||
|
|
||
|
MongoDB Engineering
@MongoDBEng
|
16. velj 2017. |
|
Integrating @aphyr’s #Jepsen into our CI presented challenges, now protects us from regressions in linearizability: engineering.mongodb.com pic.twitter.com/jUlA7eq3sW
|
||
|
||
|
Yukon Whorenelius
@aphyr
|
6. lis 2017. |
|
In this #Jepsen analysis, we look at Hazelcast: an in-memory data grid with a habit of forgetting. jepsen.io/analyses/hazel…
|
||
|
|
||
|
Yukon Whorenelius
@aphyr
|
16. velj 2017. |
|
New #Jepsen analysis: reviewing and expanding @cockroachdb's tests. We found & fixed serializability violations! jepsen.io/analyses/cockr…
|
||
|
|
||
|
Caligin Tsukihara
@Caligin35
|
1. ruj 2017. |
|
I've been experimenting with #Jepsen to check for application correctness, here's a writeup of where I got to & how: caligin.github.io/2017/08/29/exp…
|
||
|
|
||
|
Yukon Whorenelius
@aphyr
|
9. velj 2016. |
|
RethinkDB 2.2.3: A rare case of split-brain after cluster reconfiguration #jepsen aphyr.com/posts/330-jeps…
|
||
|
|
||
|
Alex
@_codejitsu
|
9. velj 2016. |
|
Interesting insights on how @DataStax uses #Jepsen for #Cassandra testing: datastax.com/dev/blog/testi…
|
||
|
|
||
|
Yukon Whorenelius
@aphyr
|
7. ožu 2018. |
|
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. jepsen.io/analyses/aeros…
|
||
|
|
||
|
Jaryd Remillard
@KarateDBA
|
31. sij |
|
Reading #jepsen posts is a 4 point story using the Fibonacci scoring
|
||
|
|
||