Skip to main content

 –

Clock skew across a Cassandra cluster

Suggest edit Updated on March 11, 2021

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.

Remedy

  • 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.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us