Actions
Bug #8891
closedrados bench hang during thrashing
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
teuthology-2014-07-20_02:30:01-rados-next-testing-basic-plana/371201
we thrash and recover but the rados bench gets stuck. it gets stuck almost immediately:
2014-07-20T10:43:58.204 INFO:teuthology.task.radosbench.radosbench.0.out:[10.214.132.36]: 70 15 634 619 35.3653 0 - 1.0567
unfortunately not much in the way of logs
Updated by Tamilarasi muthamizhan almost 10 years ago
- Assignee set to Tamilarasi muthamizhan
Updated by Tamilarasi muthamizhan almost 10 years ago
sage: also, issue 8891, adjust the nightly qa so that logging is enabled for the rados bench run. i think that means modifying radosbench.py to pass --debug-ms 1, --debug-objecter 20, debug rados = 20
Updated by Tamilarasi muthamizhan over 9 years ago
- Status changed from 12 to Resolved
added debug messages to radosbench.yaml
commit 367d4da083ea47b1de9201bbda943e57617f6701
also cherry-picked to ceph-qa-suite next branch.
Updated by Sage Weil over 9 years ago
- Status changed from Resolved to Need More Info
- Assignee deleted (
Tamilarasi muthamizhan) - Priority changed from Urgent to High
now that the logging is there we wait for it to happen again...
Updated by Sage Weil over 9 years ago
- Status changed from Need More Info to 7
- Priority changed from High to Urgent
i think this was the same repaer vs fast dispatch that i tracked down in wip-msgr.
Updated by Sage Weil over 9 years ago
- Status changed from Fix Under Review to Resolved
Actions