CassandraMetriccassandra_thread_pool_currently_blocked_tasks
Number of tasks that are currently blocked due to queue saturationDimensions:None
Available on:Native (1)
Interface Metrics (1)
Native
Number of tasks that are currently blocked due to queue saturation
Dimensions:None
Knowledge Base (1 documents, 0 chunks)
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.
Related Insights (2)
Thread Pool Saturation Causing Backpressurewarning
When Cassandra's internal thread pools (read, mutation, request, compaction) become saturated with blocked tasks, new requests queue up or fail despite available system CPU. This creates latency spikes before visible service degradation.
▸
Threadpool Saturation Blocking New Requestswarning
Cassandra's SEDA architecture relies on threadpools for async processing. When cassandra_thread_pool_count_blocked_tasks or cassandra_thread_pool_currently_blocked_tasks accumulate, requests queue waiting for threads, causing latency spikes that don't correlate with CPU/disk saturation.
▸