Skip to content

tools/cephfs: add cephfs-mdsbench metadata stress tool - #73737

Open
edwinzrodriguez wants to merge 1 commit into
ceph:mainfrom
edwinzrodriguez:cephfs-mdsbench
Open

edwinzrodriguez wants to merge 1 commit into
ceph:mainfrom
edwinzrodriguez:cephfs-mdsbench

Conversation

@edwinzrodriguez

Copy link
Copy Markdown
Contributor

cephfs-tool covers data-plane I/O, but MDS journaler/throttle stalls and Init CLIENT_CAPS storms need a client-side metadata hammer with a fixed nested tree, weighted Run mixes, and multi-process coordination. Without that, regression and performance work depends on ad-hoc scripts or proprietary suites.

Add cephfs-mdsbench (libcephfs): per-client CL{id}_MDSBENCH trees, balanced/ journal-heavy/lookup-heavy mixes, rate limiting, Init populate with optional cap-storm, ready-file start barrier, progress/JSON output, CMake install, and CephFS docs using generic software-build style wording.

Fixes: https://tracker.ceph.com/issues/83004

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. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

  • When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
Show available Jenkins commands

You must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.

cephfs-tool covers data-plane I/O, but MDS journaler/throttle stalls and
Init CLIENT_CAPS storms need a client-side metadata hammer with a fixed
nested tree, weighted Run mixes, and multi-process coordination. Without
that, regression and performance work depends on ad-hoc scripts or
proprietary suites.

Add cephfs-mdsbench (libcephfs): per-client CL{id}_MDSBENCH trees, balanced/
journal-heavy/lookup-heavy mixes, rate limiting, Init populate with optional
cap-storm, ready-file start barrier, progress/JSON output, CMake install,
and CephFS docs using generic software-build style wording.

Fixes: https://tracker.ceph.com/issues/83004
Signed-off-by: Edwin Rodriguez <edwin.rodriguez1@ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant