LinkedIn
Copied!

Table of Contents

Clock skew across a Cassandra cluster

Version:

Only available versions of this content are shown in the dropdown

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.

    Acceptable skew is 10 milliseconds.
    For more information about how to install the Network Time Protocol daemon, see your operating system's documentation.

Related Content

Did you find this content helpful?

Have a question? Get answers now.

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