Whenever using client side timestamps, whether explicitly set by the client, or set by the driver using the 2.1+ transport, the client side drivers (not just the java one) should implement a means of detecting skew (maybe as a periodic heartbeat to check every N seconds), and warn, or even optionally fail the connection, should the skew exceed a tolerable (configurable) bounds.
Environment
None
Pull Requests
None
Activity
Show:
Alex Dutra
June 21, 2020 at 5:11 PM
This ticket has been closed due to more than 2 years of inactivity, as part of an automatic housekeeping procedure.
If you think that this was inappropriate, feel free to re-open the ticket. If possible, please provide any context that could explain why the issue described in this ticket is still relevant.
Thanks for your understanding.
Bulat Shakirzyanov
December 23, 2014 at 11:36 PM
do you mean by using something like SELECT NOW() FROM system.local?
Whenever using client side timestamps, whether explicitly set by the client, or set by the driver using the 2.1+ transport, the client side drivers (not just the java one) should implement a means of detecting skew (maybe as a periodic heartbeat to check every N seconds), and warn, or even optionally fail the connection, should the skew exceed a tolerable (configurable) bounds.