-
Notifications
You must be signed in to change notification settings - Fork 7
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 when executing multiple queries scheduled synchronously. #2
Conversation
… queries were scheduled synchronously
Hello! Thanks for the PR. All driver tests use a mock server which replays cassandra packets captured by wireshark. You can copy this block to your race condition test. Something like (no setup/teardown required):
Let me know if you have any issues with it. Once the test works with the rest of the test suite I will merge it . |
Thanks! I updated the test, but there seems to be another race condition in the mock server implementation so it fails now (with real Cassandra server it passes). The error I get:
Wonder if you have any thoughts on this? Otherwise I'll try to fix this later this week. |
I have pushed a fix for the race condition in MockServer to my master branch. If you rebase and add the following teardown block to your test all tests should pass.
|
… queries were scheduled synchronously
…est execute group
Thanks! I updated my branch, though commit history got messed up after all rebases and merges. The test suite is green now. |
Race condition when executing multiple queries scheduled synchronously.
Thanks again for your PR. I have published version 0.1.5 that includes your fix. |
Hi,
Thanks for your great work on this library!
This PR is intended to fix an issue when multiple queries being scheduled synchronously and executed in parallel.
I've added a test case, but I'm not sure if it'll work with the rest of test suite, most likely not. The setup is quite complicated. If you can provide some assistance with that it would be great!