Details
Description
The scenarios:
1.
- set wallclocks in the past more that 1 year (the value of maxAcceptableLogicalClockDrift)
- a write should get through (no check for the past time) and establish a cluster time on the node to the time in the past
- now every attempt to assign logical time to current should return an error (rate error) because (wallclock time - cluster time ) > maxAcceptableLogicalClockDrift
- confirm that when the (wallclock time - cluster time ) <= maxAcceptableLogicalClockDrift it works , i.e. there are two options: