nodetool resetlocalschema

Fixes schema disagreements between nodes by dropping the schema information of the local node and resynchronizing the schema from another node. When schema information on the local node is dropped, the system schema tables are truncated. The node temporarily loses metadata about the tables on the node, but rewrites the information from another node.

nodetool resetlocal schema is useful when the table schema changes have generated too many tombstones, such as 100,000s, or when one node is out of sync with the cluster.

Synopsis

nodetool [<connection_options>] resetlocalschema

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

Reset the local schema

nodetool resetlocalschema

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2025 DataStax | Privacy policy | Terms of use | Manage Privacy Choices

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000, info@datastax.com