@@ -377,12 +377,15 @@ following:
377377* EndRun `https://endruntechnologies.com <https://endruntechnologies.com/products/ntp-time-servers >`_
378378* Netburner `https://www.netburner.com <https://www.netburner.com/products/network-time-server/pk70-ex-ntp-network-time-server >`_
379379
380- What's the maximum tolerated clock skew?
380+ Clock Skew Questions and Answers
381+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
382+
383+ **What's the maximum tolerated clock skew? **
381384
382385 By default, monitors allow clocks to drift up to a maximum of 0.05 seconds
383386 (50 milliseconds).
384387
385- Can I increase the maximum tolerated clock skew?
388+ ** Can I increase the maximum tolerated clock skew? **
386389
387390 Yes, but we strongly recommend against doing so. The maximum tolerated clock
388391 skew is configurable via the ``mon-clock-drift-allowed `` option, but it is
@@ -393,7 +396,7 @@ Can I increase the maximum tolerated clock skew?
393396 unforeseen effects on the stability of the monitors and overall cluster
394397 health.
395398
396- How do I know whether there is a clock skew?
399+ ** How do I know whether there is a clock skew? **
397400
398401 The monitors will warn you via the cluster status ``HEALTH_WARN ``. When clock
399402 skew is present, the ``ceph health detail `` and ``ceph status `` commands
@@ -410,7 +413,7 @@ How do I know whether there is a clock skew?
410413 the reported offsets of other monitors are relative to the lead monitor, not
411414 to any external reference source.
412415
413- What should I do if there is a clock skew?
416+ ** What should I do if there is a clock skew? **
414417
415418 Synchronize your clocks. Using an NTP client might help. However, if you
416419 are already using an NTP client and you still encounter clock skew problems,
0 commit comments