fix(nemesis): handle new keyspace being written to during AddRemoveDCNemesis - #15789
Open
cezarmoise wants to merge 1 commit into
Open
fix(nemesis): handle new keyspace being written to during AddRemoveDCNemesis#15789cezarmoise wants to merge 1 commit into
cezarmoise wants to merge 1 commit into
Conversation
…Nemesis If a new keyspace is created and written to by cassandra-stress while there is another DC, it because the stress command only specifies `replication_factor=3`, it will try to write to that DC and get a schema creation failure. - change the number of nodes in the new DC to 3 (matches RF in most commands) - look for keyspaces from outside the nemesis, and revert their RF if needed.
Collaborator
✅ Test Summary: PASSED✅ Precommit: PASSED
✅ Tests: PASSED
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If a new keyspace is created and written to by cassandra-stress while there is another DC, because the stress command only specifies
replication_factor=3, it will try to write to that DC and get a schema creation failure.Closes: SCT-130
Testing
Tested on another branch were I added a nemesis that runs in parallel and just creates and writes to some keyspaces
From sct.log, 4 instances where the keyspace created by the second nemesis was altered to have RF=0 on the new DC.
PR pre-checks (self review)
backportlabelsReminders
sdcm/sct_config.py)unit-test/folder)