Project

General

Profile

Feature #16523

Assert directory fragmentation is occuring during stress tests

Added by John Spray over 1 year ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Testing
Target version:
Start date:
06/27/2016
Due date:
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
User Impact:
Affected Versions:
Release:
Component(FS):
Needs Doc:
No

Description

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.

History

#1 Updated by John Spray 10 months ago

  • Assignee set to John Spray

#2 Updated by John Spray 9 months ago

  • Status changed from New to In Progress

#3 Updated by John Spray 9 months ago

  • Target version set to v12.0.0

#4 Updated by John Spray 5 months ago

  • Status changed from In Progress to Resolved
commit e90e37690abaef2debc12bac187d18eaa79c9500
Author: John Spray <john.spray@redhat.com>
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 <john.spray@redhat.com>

Also available in: Atom PDF