Ardent Performance Computing
data loss
Testing CloudNativePG Preferred Data Durability
This is the third post about running Jepsen against CloudNativePG. Earlier posts: First: shout out to whoever first came up with Oracle Data Guard Protection Modes. Designing it to be explained as a choice between performance, availability and protection was a great idea. Yesterday’s blog post described how the core of all data safety is copies of … Continue reading
Data Safety on a Budget
Many experienced DBAs joke that you can boil down the entire job to a single rule of thumb: Don’t lose your data. It’s simple, memorable, and absolutely true – albeit a little oversimplified. Mark Porter’s Cultural Hint “The Onion of our Requirements” conveys the same idea with a lot more accuracy: We need to always make sure we … Continue reading
Losing Data is Harder Than I Expected
This is a follow‑up to the last article: Run Jepsen against CloudNativePG to see sync replication prevent data loss. In that post, we set up a Jepsen lab to make data loss visible when synchronous replication was disabled — and to show that enabling synchronous replication prevents it under crash‑induced failovers. Since then, I’ve been … Continue reading
Run Jepsen against CloudNativePG to see sync replication prevent data loss
Are you in the Pacific Northwest? Want to learn more about topics related to this blog? At 3:15p on Thu Nov 13 in KubeCon Atlanta, I’ll be speaking with Leonardo Cecchi about distributed systems theory applied to standard open source postgres cluster reconfigurations. Jepsen is a testing framework for distributed systems that verifies safety guarantees … Continue reading
Disclaimer
This is my personal website. The views expressed here are mine alone and may not reflect the views of my employer.
contact: schneider @ ardentperf.com
Ardent Performance Computing 
Recent Comments