Thread pool and read/write latency statistics

The DataStax Enterprise (DSE) database maintains distinct thread pools for different stages of execution. Each thread pool provides statistics on the number of tasks that are active, pending, delayed, completed, and blocked. Increases in the Pending tasks column indicate when to add additional capacity. After a baseline is established, configure alarms for any increases above normal in the pending tasks column.

Several options are available for viewing and configuring thread pool statistics:

  • Use nodetool tpstats on the command line to view the thread pool details shown in the table.

    (DSE 6.8 | 6.7 | 6.0 | 5.1)

  • View thread pool statistics from the Node Details dialog in OpsCenter.

    (OpsCenter 6.8 | 6.7 | 6.5)

  • Configure alerts and dashboard graphs for thread pool metrics in OpsCenter Monitoring.

    (OpsCenter 6.8 | 6.7 | 6.5)

The database tracks latency (averages and totals) of read, write, and slicing operations at the server level through StorageProxyMBean.

nodetool tpstats provides the following data:


Completes background tasks like submitting hints and deserializing the row cache.


Running compaction.


Distributing node information via Gossip. Out of sync schemas can cause issues. You may have to sync using nodetool resetlocalschema. (DSE 6.8 | 6.7 | 6.0 | 5.1)


Dispatches a single hints file to a specified node in a batched manner.


Responding to non-client initiated messages, including bootstrapping and schema checking.


Writing memtable contents to disk. May back up if the queue is overruns the disk I/O, or because of sorting processes.

nodetool tpstats no longer reports blocked threads in the MemtableFlushWriter pool. Check the Pending Flushes metric reported by nodetool tablestats. (DSE 6.8 | 6.7 | 6.0 | 5.1)


Cleaning up after flushing the memtable (discarding commit logs and secondary indexes as needed).


Making unused memory available.


Calculating pending ranges per bootstraps and departed nodes. Reporting by this tool is not useful — see Developer notes.


Activity for the memtable flush writer of each disk.


Performing read repairs. Usually fast, if there is good connectivity between replicas.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000,