Clock skew across a Cassandra cluster
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.
For more information about how to install the Network Time Protocol daemon, see your operating system's documentation. Note: Acceptable skew is 10 milliseconds. Previous topic Cassandra warning: Couldn't find cfId Next topic Cassandra terminates on startup