Close popover

Table of Contents

Clock skew across a Cassandra cluster

Version:

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.

  • Troubleshooting Cassandra

    Identify the root cause of degraded performance by completing corresponding monitoring activities. Learn about the most commonly encountered Cassandra issues and how to address them.

Have a question? Get answers now.

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