Actions
Bug #41218
closedmgr/volumes: retry spawning purge threads on failure
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
mgr/volumes
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
there were no logs available for further debugging :(
Patrick saw another instance of this error with no specific reason related to mgr/volumes. There could be a possibility of a memory leak in manager and this might just be a side effect of a bigger issue.
For now, we should probably retry when a purge thread fails to spawn. But this should not be endless and there needs to be an upper cap for this, after which we log the error to cluster log and/or update status in `ceph status`.
Updated by Venky Shankar over 4 years ago
- Related to Bug #41219: mgr/volumes: send purge thread (and other) health warnings to `ceph status` added
Updated by Ramana Raja over 4 years ago
- Backport changed from luminous, mimic to nautilus
Updated by Venky Shankar over 4 years ago
thanks -- those were cache in my browser :P
Updated by Venky Shankar over 4 years ago
- Status changed from New to Fix Under Review
Updated by Patrick Donnelly over 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #41889: nautilus: mgr/volumes: retry spawning purge threads on failure added
Updated by Nathan Cutler over 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions