Bug #18004
heartbeat peers need to be updated when a new OSD added into an existed cluster
% Done:
0%
Source:
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
The case is:
There is a storage node which has two osds. nearly one min later, a new OSD joins in. Monitor sees it as "up", and no heatbeat from existing two osds to this new one. When we kill this new OSD, no osd reports this to monitor, so monitor still treats it as "up". Then, if the user invokes fio, io may hang there.
Related issues
History
#1 Updated by Samuel Just over 7 years ago
- Priority changed from Normal to High
#2 Updated by Sage Weil over 7 years ago
- Status changed from New to Resolved
#3 Updated by Kefu Chai about 6 years ago
- Copied to Backport #22794: jewel: heartbeat peers need to be updated when a new OSD added into an existed cluster added
#4 Updated by Nathan Cutler about 6 years ago
- Status changed from Resolved to Pending Backport
- Backport set to jewel
#5 Updated by Nathan Cutler about 6 years ago
- Status changed from Pending Backport to Resolved