Actions
Bug #47238
closedmgr becomes unresponsive when the progress bar is shown
% Done:
0%
Source:
Tags:
Backport:
nautilus,octopus
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
#46416 works well in that when there is no progress bar in `ceph -s`, the mgr cpu usage is low and the mgr is responsive.
However, when the progress is active, e.g. after `ceph osd out 722`, the mgr becomes unbearably slow, never responding to commands like `ceph balancer status`. The `finisher-Mgr` queue also grows into the multiple 10's of thousands.
I suspect that `progress` needs further optimizations, or at least an option to disable it.
Updated by Neha Ojha over 3 years ago
- Priority changed from Normal to Urgent
We should certainly have a way to turn the progress module off when it misbehaves.
Updated by Neha Ojha over 3 years ago
- Assignee set to Kamoltat (Junior) Sirivadhna
Updated by Neha Ojha over 3 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 37488
Updated by Josh Durgin over 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Neha Ojha over 3 years ago
- Copied to Backport #48265: nautilus: mgr becomes unresponsive when the progress bar is shown added
Updated by Neha Ojha over 3 years ago
- Copied to Backport #48266: octopus: mgr becomes unresponsive when the progress bar is shown added
Updated by Nathan Cutler about 3 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