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 July 5, 2022

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.

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.

Related articles

Troubleshooting Cassandra

Tags

Pega Platform 8.7 Decision Management

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

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