Actions
Bug #14750
closedObjecter: do not mark OSD ops as laggy based on osd_timeout value
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
We are currently looking at Objecter::osd_timeout when determining if OSD ops are laggy in Objecter::tick(). This happened in commit ecf2bebe9, which mistakenly switched it from looking at the config option objecter_timeout.
Since the osd_timeout is usually zero, meaning we don't want to get ETIMEDOUT on ops, that means that we mark ops as laggy whenever we tick(), and subscribe to osdmaps from the monitor. Yikes!
Updated by Greg Farnum about 8 years ago
- Status changed from New to 7
Actions