CASSANDRA-17999: Recreate WriteTimeoutException when using Paxos v2 in LWT performance test #205
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…using Paxos v2 in an LWT performance test that only has a single datacenter.
Author
|
Closing this PR as per this comment on Jira from Branimir Lambov, mentioning that this Python dtest is no longer required. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Recreated a WriteTimeoutException which is encountered when using Paxos v2 in an LWT performance test that only has a single datacenter because Paxos was still waiting for a response from another datacenter during the Commit/Acknowledge phase even though we were running with LOCAL_SERIAL.
patch by @marianne-manaog ; reviewed by @blambov for CASSANDRA-17999
The Cassandra Jira