A command line interface for Cassandra for managing a cluster.
If a username and password for RMI authentication are set explicitly in the cassandra-env.sh file for the host, then you must specify credentials:
|-a||--include-all-sstables||Rewrite/upgrade all SSTables including the most recent when rebuilding SSTables.|
|-et||--end-token arg||Token at which repair range ends.|
|-h||--host arg||Hostname of node or IP address.|
|-local||--in-local-dc||Only repair against nodes in the same data center.|
|-p||--port arg||Remote JMX agent port number.|
|-pr||--partitioner-range||Repair only the first range returned by the partitioner for the node.|
|-pw||--password arg||Remote JMX agent password.|
|-st||--start-token arg||Token at which repair range starts.|
|-T||--tokens||Display all tokens.|
|-u||--username arg||Remote JMX agent username.|
|Snapshot options only|
|-cf||--column-family arg||Only take a snapshot of the specified table.|
|-ns||--no-snapshot||Disables snapshot during scrub to save disk space. If the disk utilization is more than 50%, scrub fails.|
|-snapshot||--with-snapshot||Repair one node at a time using snapshots.|
|-t||--tag arg||Optional name to give a snapshot.|
Square brackets indicate optional parameters.
If you are using virtual nodes (vnodes), use nodetool status; it is much less verbose.
A probability of 1.0 will trace everything whereas lesser amounts (for example, 0.10) only sample a certain percentage of statements. Care should be taken on large and active systems, as system-wide tracing will have a performance impact. Unless you are under very light load, tracing all requests (probability 1.0) will probably overwhelm your system. Start with a small fraction, for example, 0.001 and increase only if necessary. The trace information is stored in a system_traces keyspace that holds two tables – sessions and events, which can be easily queried to answer questions, such as what the most time-consuming query has been since a trace was started. Query the parameters map and thread column in the system_traces.sessions and events tables for probabilistic tracing information.
Rebuilds SSTables on a node for the named tables that are not on the current version. Use when upgrading your server or changing compression options (available from Cassandra 1.0.4 and later).
Use -a to include all SSTables, even those already on the current version.