`nodetool cleanup`

Immediately cleans up keyspaces and tables that no longer belong to a node.

OpsCenter provides a Cleanup option in the Nodes UI for Running cleanup.

Hyper-Converged Database (HCD) does not automatically remove data from nodes that lose part of their partition range to a newly added node. After adding a new node, use nodetool cleanup on the source node and on neighboring nodes that shared the same subrange to prevent the database from including the old data to rebalance the load on that node. The nodetool cleanup command temporarily increases the use of disk space proportional to the size of the largest SSTable and may cause an increase in Disk I/O.

Failure to run nodetool cleanup after adding a node may result in data inconsistencies including resurrection of previously deleted data.

Synopsis

nodetool [<connection_options>] cleanup
[-j <num_jobs>] [--]
[<keyspace_name> <table_name> [<table_name> ...]]

Definition

The short- and long-form options are comma-separated.

Connection options

-h, --host hostname: The hostname or IP address of a remote node or nodes. When omitted, the default is the local machine.
-p, --port jmx_port: The JMX port number.
-pw, --password jmxpassword: The JMX password for authenticating with secure JMX. If a password is not provided, you are prompted to enter one.
-pwf, --password-file jmx_password_filepath: The filepath to the file that stores JMX authentication credentials.
-u, --username jmx_username: The username for authenticating with secure JMX.