-
Notifications
You must be signed in to change notification settings - Fork 600
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
Jepsen: G-nonadjacent-item #13318
Comments
When sorting by versions the order should be |
The full log shows that the max read for key 8 was Must be some kind of out-of-order execution bug. :-/ |
The first time 655 was observed was in this op:
Shard 72075186224209701 was still in |
Oh, and T4 didn't seem to use write locks. The read happened at ts |
There's also this op that received reply a bit earlier:
The read was using a snapshot 1736528601991 which is greater than T3's 1736528601840, and it obviously observed 655, otherwise it wouldn't have appended the value 656 after 655. This doesn't really say anything though. |
One idea was that |
20250110T200005.800+0300
The text was updated successfully, but these errors were encountered: