Details
-
Bug
-
Resolution: Fixed
-
None
-
None
-
*Location*: http://developer.couchbase.com/documentation/server/4.6/xdcr/xdcr-timestamp-based-conflict-resolution.html
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36
*Referrer*: http://developer.couchbase.com/documentation/server/4.6/install/synchronize-clocks-using-ntp.html
*Screen Resolution*: 1440 x 900
*Location*: http://developer.couchbase.com/documentation/server/4.6/xdcr/xdcr-timestamp-based-conflict-resolution.html *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36 *Referrer*: http://developer.couchbase.com/documentation/server/4.6/install/synchronize-clocks-using-ntp.html *Screen Resolution*: 1440 x 900
-
DOC-2022-S13
Description
When the clocks drift out of sync there's an optional alert raised on the target side.
[<DATE>] - Remote or replica mutation received for bucket "<BUCKET>" on node "<IP>" with timestamp more than 5000 milliseconds ahead of local clock. Please ensure that NTP is set up correctly on all nodes across the replication topology and clocks are synchronized.
Documentation doesn't give indication how to setup the alert for LWW.
It doesn't state how to adjust the alert threshold.
What monitoring is required and what stats are available for drift.