Skip to content
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

Closed
uncle-betty opened this issue Jun 26, 2015 · 2 comments
Closed

Race condition in workload D? #327

uncle-betty opened this issue Jun 26, 2015 · 2 comments

Comments

@uncle-betty
Copy link
Contributor

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.

@uncle-betty
Copy link
Contributor Author

Proposed fix in pull request #364.

@allanbank
Copy link
Collaborator

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants