-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Race condition in workload D? #327
Comments
Closed
Proposed fix in pull request #364. |
Merged
allanbank
added a commit
to allanbank/YCSB
that referenced
this issue
Jul 22, 2015
Closed
Closed
Not sure why it re-openned. Closing again. |
jaricftw
pushed a commit
to jaricftw/YCSB
that referenced
this issue
Jul 19, 2016
jaricftw
pushed a commit
to jaricftw/YCSB
that referenced
this issue
Jul 19, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There seems to be a race condition in workload D.
The client threads generate keys for the records to be inserted and there is a small time window between the thread generating the key and it actually inserting the record. However, as soon as the key has been generated, that key is considered to be available for other threads to read. (Because transactioninsertkeysequence.lastInt() now returns that key.) That results in the other threads potentially trying to read records that don't yet exist.
The text was updated successfully, but these errors were encountered: