Popular Apache Cassandra Problems & How to Fix 'Em
summary
Eight concrete fixes and measurable checks for Cassandra operations: run 10,000 IOPS soak test on each node to validate SSD controllers, use G1 and keep heap 20–24GB (never over 31GB) for stable GC, and disable multi data directories; use LVM to avoid known bugs. Enforce NTP and clock-drift alerts, list three seeds per DC consistently, test hint replay throttling and repair windows, and drop unused tables to cut memory and I/O.
AI-written summary · about
chapters (5)
- 0:00Introduction and scope
- 1:15Infrastructure best practices
- 2:16Configuration and tuning
- 3:14Data modeling and security
- 32:53Troubleshooting and Q&A
related talks
23mDeciphering Cassandra’s Prophecy: Preventing the Fall of Your Application
40mLatency, Throughput & Fault Tolerance: Building a Modern Database
46mApache Cassandra: 8 years in production
53mApache Cassandra. Inception - all you need to know
35mReplacing Cassandra: A Digital Transformation for the World’s Largest Digital Identity Network
39mMaking Cassandra Faster in Cloud-native architecture
52mCassandra – robisz to dobrze (...)
45mCassandra Architecture: Understanding, Scaling and Optimizing