nodetool relocatesstables
Rewrites SSTables to the correct disk.
Use with JBOD disk storage to manually rewrite the location of SSTables on disk. Useful if you have changed the replication factor for the cluster or if you added a new disk.
Synopsis
nodetool [<connection_options>] relocatesstables
[-j <num_jobs>] [--] <keyspace_name> <table_name>
Syntax conventions | Description |
---|---|
UPPERCASE |
Literal keyword. |
Lowercase |
Not literal. |
<`Italics>` |
Variable value. Replace with a valid option or user-defined value. |
|
Optional.
Square brackets ( |
|
Group.
Parentheses ( |
|
Or.
A vertical bar ( |
|
Repeatable.
An ellipsis ( |
|
Single quotation ( |
|
Map collection.
Braces ( |
|
Set, list, map, or tuple.
Angle brackets ( |
|
End CQL statement.
A semicolon ( |
|
Separate the command line options from the command arguments with two hyphens ( |
|
Search CQL only: Single quotation marks ( |
|
Search CQL only: Identify the entity and literal value to overwrite the XML element in the schema and solrconfig files. |
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.
Command arguments
--
-
Separates an option from an argument that could be mistaken for an option.
- -j, --jobs num_jobs
-
-
num_jobs - Number of SSTables affected simultaneously. Default: 2.
-
0 - Use all available compaction threads.
-
- keyspace_name
-
The keyspace name.
- table_name
-
The table name.
Examples
Relocate SSTables after adding a new disk
nodetool relocatesstables cycling birthday_list
If the SSTables are on the correct disk already, no action is taken.