Expedited Repair Service configuration

About this task

To repair one or more nodes as quickly as possible without regard to application performance, use the Repair Service to repair the entire cluster. Tell the Repair Service to run as fast as it can without severely impacting cluster performance.


  1. Stop the Repair Service.

  2. Restart Repair Service with a very low time-to-complete value, such as .01 days.

    The Repair Service logs warn that the Repair Service cannot be completed within .01 days. This is expected. The Repair Service continues to run.

    The Repair Service runs its maximum number of parallel repair tasks and avoid any delays between tasks. The status of the running repair cycle can be seen in the Repair Service UI as a progress bar. Once this cycle completes, a new cycle starts and resets the progress bar.

  3. Once one full cycle has been completed with this time-to-complete setting, restart the Repair Service with your standard time-to-complete value.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

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