Actions
Bug #46440
closedmgr: don't update osd stat which is already out
% Done:
0%
Source:
Community (dev)
Tags:
Backport:
octopus, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
When our OSDs get hang and have slow requests, we try to identify the strange hang issue and also let the cluster get back to normal by setting noup flag and then marking OSD down and out. The cluster still reports slow requests on this OSD as a false alarm.
We found when orignal PG monitor handled PGSTATS msg, it wouldn't update osd stat if this OSD is not in OSD map, but current MGR had no checks on that.
Updated by Kefu Chai almost 4 years ago
- Status changed from New to Fix Under Review
- Assignee set to Zhi Zhang
Updated by Kefu Chai over 3 years ago
- Status changed from Fix Under Review to Resolved
Updated by Igor Fedotov over 3 years ago
- Status changed from Resolved to Pending Backport
- Backport set to octopus, nautilus
Updated by Igor Fedotov over 3 years ago
- Related to Bug #48385: nautilus: statfs: a cluster with any up but out osd will report bytes_used == stored added
Updated by Igor Fedotov over 3 years ago
- Copied to Backport #48400: nautilus: mgr: don't update osd stat which is already out added
Updated by Igor Fedotov over 3 years ago
- Copied to Backport #48401: octopus: mgr: don't update osd stat which is already out added
Updated by Igor Fedotov over 3 years ago
- Status changed from Pending Backport to Resolved
Actions