Bug #12657
closed
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?
- Assignee set to John Spray
- 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.
Also available in: Atom
PDF