Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Clock skew across a Cassandra cluster

Updated on May 17, 2024

This content applies only to On-premises and Client-managed cloud environments

Clock skew across a Cassandra cluster can cause synchronization and replication issues.

For example, data might reappear after deletion, or seemingly successful modifications might not be visible.


  • Use the Network Time Protocol daemon to synchronize clocks for all nodes in the cluster.
    Note: Acceptable skew is 10 milliseconds.
    For more information about how to install the Network Time Protocol daemon, see your operating system's documentation.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us