Actions
Bug #20118
closedTest failure: test_ops_throttle (tasks.cephfs.test_strays.TestStrays)
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Testing
Target version:
-
% Done:
0%
Source:
Q/A
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):
Description
# Check that we got up to a respectable rate during the purge. This is totally # racy, but should be safeish unless the cluster is pathologically slow, or # insanely fast such that the deletions all pass before we have polled the # statistics. if throttle_type == self.OPS_THROTTLE: if ops_high_water < mds_max_purge_ops / 2: raise RuntimeError("Ops in flight high water is unexpectedly low ({0} / {1})".format( ops_high_water, mds_max_purge_ops )) elif throttle_type == self.FILES_THROTTLE: if files_high_water < mds_max_purge_files / 2: raise RuntimeError("Files in flight high water is unexpectedly low ({0} / {1})".format( ops_high_water, mds_max_purge_files ))
the ops_high_water check failed. The check is too racy. the timing of evaluating delayed strays and receiving cap releases affect the check.
Updated by Patrick Donnelly almost 7 years ago
- Category set to Testing
- Status changed from New to 12
- Source set to Q/A
Updated by Patrick Donnelly almost 7 years ago
- Is duplicate of Bug #16881: RuntimeError: Files in flight high water is unexpectedly low (0 / 6) added
Updated by Patrick Donnelly almost 7 years ago
- Status changed from 12 to Duplicate
Actions