verification of osd_scrub_load_threshold with high CPU load using stress-ng #5565
+1,221
−588
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.
Description
The Fix includes the -
Automation to verify the osd_scrub_load_threshold with high CPU load using stress-ng.
a. Install stress-ng package on all rados nodes
b. Start stress-ng to continuously generate load
c. Monitoring load continuously to verify it increases and calculate load threshold.The formula used to calculate the load is-
Load_threshold = load_avgerage / online_cpu_count
Where
Load average is clculated by executing the "/proc/loadavg" command
online_cpu_count is found by executing the nproc command
d. Wait for load threshold (loadavg / online CPUs) to exceed 15
e. Set the osd_scrub_load_threshold to 10(Default)
f. Set the debug_osd and debug_mon to 20
g. Start the user initiated scrub and check that the scrub should not get start if the load is high
h. Check logs for scrub_load_below_threshold messages
Divided the scenarios in to separate tests
Uncommented the Verification of the osd_scrub_load_threshold parameter with the default value which is 10.0
Abandoning the following PR due to history issues and I re-open this new PR.All the review commnets can see at the below PR.
PR - #5549
Please include Automation development guidelines. Source of Test case - New Feature/Regression Test/Close loop of customer BZs
click to expand checklist