Clock Synchronization, Affiliated FTL Servers, and Persistence

Persistence services depend on clock synchronization among their host computers.

Ensure clock synchronization among affiliated persistence service hosts to within a few milliseconds.

When persistence services in a cluster communicate with one another, they rely on timestamps that they receive from their FTL servers. If a persistence service moves to a different host computer, and its clock is not synchronized with the previous host, then the persistence services could have difficulty forming a quorum.

For example, this difficulty could occur after switching operations to a disaster recovery site.

If you encounter this difficulty, consider forcing a quorum; see Before Forcing a Quorum.