CassandraMetriccassandra_sstable
Number of SSTables on disk for a given tableDimensions:None
Available on:Native (1)
Interface Metrics (1)
Knowledge Base (10 documents, 0 chunks)
guideCritical Cassandra Performance Metrics to Monitor - Sematext2324 wordsscore: 0.95This comprehensive guide explains critical Cassandra performance metrics to monitor, covering node availability, compaction metrics, read/write performance, table-level metrics including partition size and tombstones, and cache utilization. It provides context on Cassandra architecture and explains why each metric category matters for cluster health and performance.
guideCompaction in Cassandra | Datavail1441 wordsscore: 0.65This guide explains Cassandra's compaction process, including different compaction strategies (STCS, LCS, DTCS, TWCS), tuning parameters, and performance impacts. It covers when to use each strategy and how to troubleshoot compaction-related performance issues like slow reads and node unreachability.
troubleshootingCassandra Node unable to compact - Stack Diagnosis489 wordsscore: 0.72This page provides troubleshooting guidance for Cassandra nodes unable to complete compaction due to resource constraints. It covers root causes like insufficient disk space, memory, and CPU, along with resolution steps including resource allocation adjustments, compaction strategy changes, and monitoring recommendations.
blog post|
Compaction Strategies, Performance, and Their Impact on Cassandra Node Density1766 wordsscore: 0.65This blog post examines how different compaction strategies in Apache Cassandra impact node density and cost efficiency. It covers the trade-offs of STCS, LCS, and TWCS, and advocates for the new UnifiedCompactionStrategy (UCS) in Cassandra 5.0 as a game-changer that combines benefits of previous strategies while maintaining controlled SSTable sizes.
guideCassandra Performance: The Most Comprehensive Overview You’ll Ever See3493 wordsscore: 0.72This comprehensive guide explains Cassandra performance fundamentals including data modeling, partitioning, denormalization, and write/read operations. It covers internal mechanisms like memtables, SSTables, commit logs, and the token ring architecture. While not explicitly focused on monitoring, it provides deep operational context essential for understanding what to monitor and why certain metrics matter.
troubleshootingbigdata - Cassandra low read performance with high SSTable count - Stack Overflow1958 wordsscore: 0.72A Stack Overflow question discussing Cassandra read performance issues related to high SSTable count. The discussion covers interpreting nodetool cfstats output, understanding SSTable distribution, and recommendations for compaction strategy selection (SizeTieredCompactionStrategy vs LeveledCompactionStrategy) to improve read performance.
troubleshootingflush_largest_memtables_at messages in 7.42262 wordsscore: 0.72This is a mailing list discussion about troubleshooting Cassandra 7.4 heap memory usage and memtable flushing warnings. The thread covers analyzing memtable flush behavior, key cache hit rates, and heap utilization through nodetool commands and cfstats output.
troubleshootingKey Concepts: Cassandra Heap Issues666 wordsscore: 0.75This page provides troubleshooting guidance for Cassandra heap memory issues and Out Of Memory (OOM) exceptions. It explains common causes including memtables, read patterns, repair operations, and compactions, along with diagnostic approaches using nodetool commands and potential workarounds for heap pressure.
troubleshootingResolving Cassandra Query Timeout Issues: Optimizing Performance and Ensuring Stability - Proactive Insights and Support For Open-Source Applications376 wordsscore: 0.65This page describes a case study of resolving Cassandra query timeout issues in a production environment. It covers troubleshooting steps including investigating cluster health, reviewing table sizes and SSTables, and implementing solutions like increasing timeout configurations and adding indexes to improve query performance.
best practicesWhat you should understand before using Apache Cassandra in production | Running Code606 wordsscore: 0.75This blog post explains Cassandra's storage architecture (memtables, SSTables, and compaction) and emphasizes a critical operational best practice: setting disk space alerts at 50% rather than the typical 80-90% threshold. This is because compaction requires approximately 50% free disk space to merge SSTables, and without compaction, disk space cannot be freed, creating an operational crisis.
Related Insights (2)
Cache Miss Rate Amplifying Read Latencywarning
When cassandra_key_cache_hit_rate drops significantly below historical baseline, reads bypass cache and hit disk directly, multiplying I/O load and latency. This often correlates with workload changes or cache size misconfiguration.
▸
Compaction Backlog Choking Read Performancewarning
When pending compaction tasks accumulate, read latency degrades because queries must scan many SSTables. This manifests as rising P99 read latency while write latency remains stable, often accompanied by increasing SSTables-per-read counts.
▸