Can you really say data loss is a *myth* if it's still the default behavior? https://developer.mongodb.com/article/everything-you-know-is-wrong#myth-7--mongodb-loses-data
Can you believe it?! We're adding ONE more speaker to #YOW20 and it's @aphyr!
We trust databases to store our data, but should we? Learn the basics of distributed systems testing & advice for testing your own systems in his keynote - Jepsen 13.
Happy to announce Jepsen 0.2.1 is now available: https://github.com/jepsen-io/jepsen/releases/tag/0.2.1
Jepsen's AWS Marketplace product (launches a whole Jepsen cluster in a few clicks) has been updated for Debian Buster, and now includes additional dependencies you'll want for running tests based on Elle. Happy testing!
@rior 20% of the time, it's isolated 100% of the time
Put a bunch of work into the Jepsen docker-compose setup, and I'm pleased to report it now gives you a full Debian Buster cluster with keys and dependencies out of the box--should be good for running the latest tests. Hopefully this helps!
Do you use Cassandra or another CQL-compatible database? I'd like to hear your perspective on adding things to a CQL set: https://docs.google.com/forms/d/e/1FAIpQLSc5EqGjHA6HwXcvm5Om0jfNjaiKybHLjeppB32K502Amdsa8g/viewform?usp=sf_link
A bug in Jepsen: from versions 0.1.2 to 0.2.0, the counter checker docstring incorrectly claimed to handle decrements, which could cause valid histories to be reported as failures. This did not affect official Jepsen reports, but other counter tests using decrements may have been affected: https://groups.google.com/u/1/a/jepsen.io/g/announce/c/GsQ6e2e-Mcs
@rior It's not static.
@rior I'm... hoping not to have to redo my entire deployment scheme every 2 years but this appears to be the hellscape we're headed into
mostly it's like
I KNOW AppEngine Flex's problems. What I *don't* know is how GKE is going to ruin my life.
Love this thing where Google Cloud decides that jepsen.io has been stable for a while and it really ought to do something about that, so it kills the VM and spins up a new one to replace it only *after* it's dead, resulting in ~10 minutes of spurious downtime.
It's been doing this for ~two years, COME ON Google, y'all are supposed to be experts at rollouts. Start new nodes *before* you kill existing ones!
Did an interview with Tobias Macey talking about Jepsen's design, software verification in general, and the distributed database landscape: https://www.dataengineeringpodcast.com/jepsen-distributed-systems-testing-episode-143/
@dotemacs Yeah, I think it'll be posted here after the Zoom: https://www.youtube.com/playlist?list=PLSE8ODhjZXjagqlf1NxuBQwaMkrHXi-iz
Reminder: The @jepsen_io Quarantine DB Talk featuring Kyle Kingsbury (@aphyr) is next Monday July 27 @ 4:30pm ET. Video will be live and uncut for the public over Zoom. All are welcome to join. https://db.cs.cmu.edu/events/db-seminar-spring-2020-db-group-black-box-isolation-checking-with-elle/
@dotemacs July 27th is in the future so... no?
Hello #clojure friends
If you have some free time and you know #jepsen, this might be relevant for you
@rior Yeah, students have gotten in touch from time to time, but none of them have started the actual thesis yet to my knowledge. Sometimes academics just... pass off a bunch of Jepsen work as their own too, that's fun. ;-)