Materialized views maintenance guidelines

Follow these guidelines to ensure materialized view health and consistency:

  • Run anti-entropy repair on base tables with materialized views at least every gc_grace_seconds to ensure tombstones are propagated to materialized views and avoid the data resurrection problem.

  • Enable NodeSync on base tables with materialized views. See Enabling NodeSync validation.

  • Optionally, run periodic repairs on materialized views to detect and fix silent data corruption. Repairs on materialized views can be run at a lower periodicity than base tables.

    Use the NodeSync deadline_target_sec parameter to control the periodicity at which data is validated on base tables and materialized views. See Setting the NodeSync deadline.

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,