-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[Jepsen] Snapshot Isolation (SI) violation under huge clock skew even if it is bounded by max_clock_skew_usec flag #975
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I was able to reproduce bank account test failure under high clock skew and tracked down to a transaction which broke the total sum along with its read_time and other info, both conflicting transactions were applied.
Transaction 1aa7ccd8-fd49-4803-8b9b-9d6fc1a68d43 is using But between Some related logs:
|
Finally found a bug in
So, in case
failed status won't be saved into
|
Commit: db46ef9 |
After the fix (db46ef9) the bug is no longer reproducible even with clock skew higher than |
Tested with |
In this test |
Uh oh!
There was an error while loading. Please reload this page.
@ttyusupov caught an issue with bank account test - total sum diverges under huge clock skew nemesis even if clock skew is bounded by
max_clock_skew_usec
flag.How to reproduce:
yugabyte/src/auto.clj
: add setting max clock skew to 1000000 secounds:on a GCP cluster - 5 separate debian jessie instances.
This test introduces random clock bumps up to 262 seconds in both directions and random clock strobes from 4 ms to 262 seconds, with a period of 1 ms to 1 second, for a duration of 0-32 seconds (every period ms, adjusts the clock forward by delta ms, or, alternatively, back by delta ms. Does this for duration seconds).
If we reduce delta for both bumps and strobes to 131 seconds - test passes.
The text was updated successfully, but these errors were encountered: