[Backport 2024.2] fix(test-case): update 5000 tables test case configuration #9846
Conversation
This file contains 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
vponomaryov
force-pushed
the
backport/9843/to-2024.2
branch
from
05d0c62 to
7ad25d4
Compare
2 tasks
|
Unit tests will start working after the backport of the following PR: |
List of changes: - Disable per-table metrics due to significant perf impact. - Enable cluster health checks which work with this case just fine. - Decrease the nemesis interval from 60 minutes to just 3 keeping in mind that health checks will take some time too. - Reduce stress time for each of the 5000 commands. Having 20 minutes per cmd we will get about 1.5 days long test runs instead of the 2.5 days. - Reduce number of loaders from 5 to 3 to use resources more efficiently. In current case the bottleneck is the RAM. Note that this scenario hits following bug: - scylladb/scylla-enterprise#5093 If 'destroy_data_then_repair' nemesis gets triggered aganst the setup of this scenario. (cherry picked from commit 0c7fa60)
vponomaryov
force-pushed
the
backport/9843/to-2024.2
branch
from
7ad25d4 to
cd66fed
Compare
vponomaryov
approved these changes
Jan 22, 2025
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.
List of changes:
Note that this scenario hits following bug:
If
destroy_data_then_repairnemesis gets triggered aganst the setup of this scenario.Testing
PR pre-checks (self review)
backportlabelsReminders
Add New configuration option and document them (in
sdcm/sct_config.py)Add unit tests to cover my changes (under
unit-test/folder)Update the Readme/doc folder relevant to this change (if needed)
(cherry picked from commit 0c7fa60)
Parent PR: #9843