Database Reference
In-Depth Information
Receiving 33 files, 1612364017 bytes total
bin/../data/data/stresscql/
blogposts-946f4e60761911e4a6ea7d86f73d83eb/
stresscql-blogposts-tmp-ka-35-Data.db 27898542/27898542
bytes(100%) received from idx:0/10.10.21.228
bin/../data/data/stresscql/
blogposts-946f4e60761911e4a6ea7d86f73d83eb/
stresscql-blogposts-tmp-ka-50-Data.db 36126372/36126372
bytes(100%) received from idx:0/10.10.21.228
[ -- snip -- ]
$ bin/nodetool -h cassandra01.naishe.in netstats
Mode: NORMAL
Not sending any streams.
Read Repair Statistics:
Attempted: 0
Mismatch (Blocking): 0
Mismatch (Background): 0
Pool Name Active Pending Completed
Commands n/a 0 1154
Responses n/a 0 554
status
The
status
command is the most frequently used command. Whenever you want to in-
vestigate the ring, this is likely to be the first command you will want to run. The
status
command is a general ring health check and it gives a human-readable summary
of the cluster. Here is an example of this command, wherein the command was run twice,
once while adding a new node and then after the node joined the ring:
# A new node is joining the cluster
$ bin/nodetool status
Datacenter: us-east
===================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host
ID Rack
