Actions
Bug #40726
open"OSD::osd_op_tp thread 0x7f6dafcf0700' had timed out after 15"
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
osd.7 was marked down by itself because of unhealthy heartbeat.
2019-07-11T05:32:00.028+0000 7f6dd286d700 1 heartbeat_map is_healthy 'OSD::osd_op_tp thread 0x7f6dafcf0700' had timed out after 15 2019-07-11T05:32:00.028+0000 7f6dd286d700 1 heartbeat_map is_healthy 'OSD::osd_op_tp thread 0x7f6daf4ef700' had timed out after 15 2019-07-11T05:32:00.028+0000 7f6dd286d700 10 osd.7 284 internal heartbeat not healthy, dropping ping request
/a/kchai-2019-07-11_01:43:21-rados-wip-kefu-testing-2019-07-09-1756-distro-basic-mira/4110068
checked mira115 which hosted osd.7, no suspicious dmesg message found.
Updated by Greg Farnum almost 5 years ago
This happens occasionally on Mira nodes; but if it pops up repeatedly on the same node or test suite that may be evidence of something else.
Actions