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
qa: lower mds_session_metadata_threshold for tests #53873
Conversation
jenkins retest this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For first commit message,it'll be useful to explain why are increasing and decreasing these certain numbers.
For second commit message, s/md_thresh_evicted/mdthresh_evicted
is part of commit title as well as body. It'll be fine if we move it entirely to the body.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fair enough.
Not really - only the commit title. |
... and increase the number of files that are created so as to hit the threshold with a high probability. Fixes: http://tracker.ceph.com/issues/62873 Signed-off-by: Venky Shankar <vshankar@redhat.com>
…hresh_evicted Signed-off-by: Venky Shankar <vshankar@redhat.com>
Added some code commentary and pushed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still not happy with 100000 as a reasonable number of files for a test, and in general with the hardcoded magic numbers which are hard to relate to (why is 5000 low? compared to what?) but given your suggestion to clean up I'll approve the change.
Yeh - those magic numbers are hard to maintain. Let's plan a cleanup. |
... and increase the number of files that are created so as to hit the threshold.
Fixes: http://tracker.ceph.com/issues/62873
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test dashboard cephadm
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox
jenkins test windows