Assert directory fragmentation is occuring during stress tests
Currently we enable fragmentation and set a low (100) frag size limit, but nothing actually validates that there is any splitting going on, especially during thrashing runs where we care the most.
We have performance counters on the MDS that will tell us if splitting has occurred, but they will reset when MDSs restart.
We could add something to the thrasher task that captures MDS counters before shutting down, and accumulates values. We don't necessarily need this on every task, just something in there to check that splitting is really happening during at least some stress testing.
#4 Updated by John Spray over 2 years ago
- Status changed from In Progress to Resolved
commit e90e37690abaef2debc12bac187d18eaa79c9500 Author: John Spray <firstname.lastname@example.org> Date: Wed Mar 8 11:05:00 2017 +0000 qa/tasks: add check_counter.py We need this for CephFS, to verify that workloads we expect to do a particular thing (like directory fragmentation or metadata exports) are really doing it. This is for giving us confidence in our coverage of these features rather than testing them per se. Fixes: http://tracker.ceph.com/issues/16523 Signed-off-by: John Spray <email@example.com>