CassandraMetriccassandra_compaction_size_compacted
Total number of bytes compacted since server startDimensions:None
Available on:Native (1)
Interface Metrics (1)
Native
Total number of bytes compacted since server start
Dimensions:None
Knowledge Base (6 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.
documentationCassandra Disk Usage Explained - Instaclustr283 wordsscore: 0.72This page explains Cassandra disk usage metrics and provides operational guidance for managing disk space on Cassandra nodes. It recommends maintaining disk usage below 70% during normal operations with a minimum of 30% free space to allow for compaction and other temporary operations.
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 (3)
Compaction Strategy Mismatch Degrading Node Densitywarning
Using STCS (Size-Tiered) creates unbounded SSTable growth and prevents fast streaming, while LCS (Leveled) causes excessive write amplification under heavy load. Both reduce effective node density and operational efficiency compared to UCS (Unified) in Cassandra 5.0+.
▸
Trie-based SSTable format replaces BTree SSTableswarning
▸
Unified Compaction Strategy consolidates compaction strategieswarning
▸