nodetool checktokenmetadata
Compares the endpointState
from gossip with the TokenMetadata
on the node, and displays any mismatches between these two views of the cluster topology.
To prevent possible data loss for a node that contains mismatching cluster topology information, restart the node.
Synopsis
nodetool [<connection_options>] checktokenmetadata
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
This command takes no arguments.
Examples
Compare the cluster topology views on the node
To find mismatches between the endpointState
from gossip and the TokenMetadata
on the node, run the following command:
nodetool checktokenmetadata
If the topology views match on a node, the command returns no output.
If the topology view of the cluster between the two sources does not match on a node, the result indicates the mismatched node.
For example, the following response shows a mismatch on node 192.0.2.2
.
To fix this mismatch issue, restart the node.
Mismatch on : 192.0.2.2
Gossip tokens: -5881653292327383884,-1867202278918369648,1616284166271244128,7958092618706956678
TokenMetadata: -8952303318017438439,-8827932705200900856,-7588862910730136993,-6633932733059898331