Project

General

Profile

Actions

Bug #12657

closed

Failure in TestStrays.test_ops_throttle

Added by John Spray over 8 years ago. Updated over 8 years ago.

Status:
Can't reproduce
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Actions #1

Updated by John Spray over 8 years ago

This purged 1600 strays in 6 seconds (and therefore wasn't busy doing so for long enough to hit the required high water mark of the rate). It was meant to be throttled. What went wrong?

Actions #2

Updated by Greg Farnum over 8 years ago

  • Assignee set to John Spray
Actions #3

Updated by John Spray over 8 years ago

  • Status changed from New to Can't reproduce

Hmm, now this looks like a teuthology burp. The stats polling is meant to happen every second, but in this instance there is an unexplained 5 second delay in the log between issuing the "perf dump" and getting the result. The MDS log indicates that progress is being made and the lock is being relinquished during this period, so it's not at fault.

Let's come back to this if we see it again -- we can always make this test less sensitive by making it longer-running with more files in the workload, but I don't want to do that lightly because it's a pain when running the test interactively.

Actions

Also available in: Atom PDF