Operatoration Testing of Cluster
summary
DataStax runs nightly ephemeral clusters for connectivity and security checks, weekly 48‑hour soak tests on ~45‑node DSC clusters, and multi‑week runs on geo clusters (3 DCs, ~1990 nodes) to validate upgrades, DC add/remove, rebuilds and BC/DR. Automation uses Fallout (open‑sourced orchestration), a C‑tool component and NoSQLBench for realistic workloads. Tests produce 13+ scenario reports, runbooks and a datasheet that shortens application onboarding, establishes reference architectures and proves configurations at scale.
AI-written summary · about
chapters (7)
- 0:00Operational testing in Cassandra
- 1:47Operator vs developer personas
- 3:11Defining operational testing
- 5:36From point-in-time to continuous testing
- 7:44Key ingredients for testing
- 9:33Automated testing infrastructure
- 12:37Testing outcomes and takeaways
related talks
35mDataStax Enterprise on DC/OS - Yes, It’s Possible; Customer Case Studies
32mDataStax Enterprise on DC/OS - Yes, It’s Possible; Customer Case Studies
38mDeploying Database Clusters in the Cloud
35mMission Critical Data, and Evaluating the Community in OSS Tech
24mZero Downtime Mastering Cassandra Live Migrations at Scale
46mCassandra Serving Netflix @ Scale
43mSponsored Session: Operational Data Stores for Financial Risk Mitigation
06mLightning Talk: Performance Testing of FoundationDB using TPC-C