Illustration Image

Cassandra.Link

The best knowledge base on Apache Cassandra®

Helping platform leaders, architects, engineers, and operators build scalable real time data platforms.

9/23/2020

Reading time:1 min

nodetool tpstats

by John Doe

Provides usage statistics of thread pools.Provides usage statistics of thread pools.Synopsisnodetool <options> tpstatsCassandra tarball installations:installation_location/cassandra/binDescriptionCassandra is based on a Staged Event Driven Architecture (SEDA). Cassandra separates different tasks into stages connected by a messaging service. Each stage has a queue and a thread pool. Although some stages skip the messaging service and queue tasks immediately on a different stage when it exists on the same node. Cassandra can back up a queue if the next stage is too busy and lead to a performance bottlenecks. Thenodetool tpstatscommand reports on each stage of Cassandra operations by thread pool:Reports are updated when SSTables change through compaction or flushing.Run nodetool tpstats on a local node to get statistics for the thread pool used by the Cassandra instance running on that node.Run nodetool tpstats with the appropriate options to check the thread pool statistics for a remote node. For setup instructions, see Secure JMX Authentication.nodetool tpstats pool names and tasksThis table describes the Cassandra task or property associated with each pool name reported in the nodetool tpstats output: nodetool tpstats droppable messagesCassandra generates the messages listed below, but discards them after a timeout. The nodetool tpstats command reports the number of messages of each type that have been dropped. You can view the messages themselves using a JMX client.ExampleRunning nodetool tpstats on the host labcluster:nodetool -h labcluster tpstatsExample output is:Pool Name Active Pending Completed Blocked All time blockedCounterMutationStage 0 0 0 0 0ReadStage 0 0 103 0 0RequestResponseStage 0 0 0 0 0MutationStage 0 0 13234794 0 0ReadRepairStage 0 0 0 0 0GossipStage 0 0 0 0 0CacheCleanupExecutor 0 0 0 0 0AntiEntropyStage 0 0 0 0 0MigrationStage 0 0 11 0 0ValidationExecutor 0 0 0 0 0CommitLogArchiver 0 0 0 0 0MiscStage 0 0 0 0 0MemtableFlushWriter 0 0 126 0 0MemtableReclaimMemory 0 0 126 0 0PendingRangeCalculator 0 0 1 0 0MemtablePostFlush 0 0 1468 0 0CompactionExecutor 0 0 254 0 0InternalResponseStage 0 0 1 0 0HintedHandoff 0 0 0 Message type DroppedRANGE_SLICE 0READ_REPAIR 0PAGED_RANGE 0BINARY 0READ 0MUTATION 180_TRACE 0REQUEST_RESPONSE 0COUNTER_MUTATION 0

Illustration Image

Provides usage statistics of thread pools.

Provides usage statistics of thread pools.

Synopsis

nodetool <options> tpstats
Cassandra tarball installations:
installation_location/cassandra/bin

Description

Cassandra is based on a Staged Event Driven Architecture (SEDA). Cassandra separates different tasks into stages connected by a messaging service. Each stage has a queue and a thread pool. Although some stages skip the messaging service and queue tasks immediately on a different stage when it exists on the same node. Cassandra can back up a queue if the next stage is too busy and lead to a performance bottlenecks.

Thenodetool tpstatscommand reports on each stage of Cassandra operations by thread pool:Reports are updated when SSTables change through compaction or flushing.

Run nodetool tpstats on a local node to get statistics for the thread pool used by the Cassandra instance running on that node.

Run nodetool tpstats with the appropriate options to check the thread pool statistics for a remote node. For setup instructions, see Secure JMX Authentication.

nodetool tpstats pool names and tasks

This table describes the Cassandra task or property associated with each pool name reported in the nodetool tpstats output:

nodetool tpstats droppable messages

Cassandra generates the messages listed below, but discards them after a timeout. The nodetool tpstats command reports the number of messages of each type that have been dropped. You can view the messages themselves using a JMX client.

Example

Running nodetool tpstats on the host labcluster:

nodetool -h labcluster tpstats

Example output is:

Pool Name                    Active   Pending      Completed   Blocked  All time blocked
CounterMutationStage              0         0              0         0                 0
ReadStage                         0         0            103         0                 0
RequestResponseStage              0         0              0         0                 0
MutationStage                     0         0       13234794         0                 0
ReadRepairStage                   0         0              0         0                 0
GossipStage                       0         0              0         0                 0
CacheCleanupExecutor              0         0              0         0                 0
AntiEntropyStage                  0         0              0         0                 0
MigrationStage                    0         0             11         0                 0
ValidationExecutor                0         0              0         0                 0
CommitLogArchiver                 0         0              0         0                 0
MiscStage                         0         0              0         0                 0
MemtableFlushWriter               0         0            126         0                 0
MemtableReclaimMemory             0         0            126         0                 0
PendingRangeCalculator            0         0              1         0                 0
MemtablePostFlush                 0         0           1468         0                 0
CompactionExecutor                0         0            254         0                 0
InternalResponseStage             0         0              1         0                 0
HintedHandoff                     0         0              0   
Message type           Dropped
RANGE_SLICE                  0
READ_REPAIR                  0
PAGED_RANGE                  0
BINARY                       0
READ                         0
MUTATION                   180
_TRACE                       0
REQUEST_RESPONSE             0
COUNTER_MUTATION             0

Related Articles

data.processing
cassandra
nvidia

GitHub - fversaci/cassandra-dali-plugin: Cassandra plugin for NVIDIA DALI

fversaci

8/17/2023

cassandra
prisma

Checkout Planet Cassandra

Claim Your Free Planet Cassandra Contributor T-shirt!

Make your contribution and score a FREE Planet Cassandra Contributor T-Shirt! 
We value our incredible Cassandra community, and we want to express our gratitude by sending an exclusive Planet Cassandra Contributor T-Shirt you can wear with pride.

Join Our Newsletter!

Sign up below to receive email updates and see what's going on with our company

Explore Related Topics

AllKafkaSparkScyllaSStableKubernetesApiGithubGraphQl

Explore Further

cassandra