YugabyteDB needs max_clock_skew_usec set to 2x expected worst skew

Set maxclockskew_usec to 2x your expected worst-case clock skew between nodes when starting YB-TServers and YB-Masters; e.g. 500000 for 250ms of expected skew. Keep clock drift under 500 PPM per node and run NTP or chrony everywhere. Never set the bound below what your hardware or cloud provider guarantees.

Context: Official deploy checklist: documents the gotcha that YugabyteDB needs maxclockskew_usec set explicitly when starting servers. Set it to two times the expected maximum clock skew between any two nodes. If you set it lower than the actual skew, nodes get stopped for availability or ACID consistency breaks.

Matched source

Source: Published skill Original query: "YugabyteDB needs maxclockskew_usec set to 2x expected worst skew" Key terms: clock, expected, needs, skew, usec, worst, yugabytedb

Source: Official deploy checklist: documents the gotcha that YugabyteDB needs maxclockskew_usec set explicitly when starting servers. Set it to two times the expected maximum clock skew between any two nodes. If you set it lower than the actual skew, nodes get stopped for availability or ACID consistency breaks.

Verified resolution: Set maxclockskew_usec to 2x your expected worst-case clock skew between nodes when starting YB-TServers and YB-Masters; e.g. 500000 for 250ms of expected skew. Keep clock drift under 500 PPM per node and run NTP or chrony everywhere. Never set the bound below what your hardware or cloud provider guarantees.

Source URL: https://github.com/ddhodge/yugabyte-db/blob/HEAD/docs/content/stable/deploy/checklist.md