Actions
Bug #62165
closed[pg-autoscaler] Peformance issue with the autoscaler when we have ~32768 PGs
Status:
Resolved
Priority:
High
Assignee:
Category:
pg_autoscaler module
Target version:
-
% Done:
100%
Source:
Tags:
backport_processed
Backport:
reef, quincy, pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
We have observed a performance issue regarding the autoscaler while scale testing using reef. The cpu peaking to up to a core every minute
Files
Updated by Kamoltat (Junior) Sirivadhna 9 months ago
- Pull request ID set to 52633
The problem is due to how we have been extravagantly using osdmap get calls in the autoscaler module which becomes very costly when there is a lot of PGs.
Also attaching PR id.
Updated by Kamoltat (Junior) Sirivadhna 9 months ago
- Subject changed from [pg-autoscaler] Peformance issue with 32768 taking up 1 whole cpu core to [pg-autoscaler] Peformance issue with the autoscaler when we have ~32768 PGs
Updated by Kamoltat (Junior) Sirivadhna 8 months ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to reef, quincy, pacific
Updated by Backport Bot 8 months ago
- Copied to Backport #62885: reef: [pg-autoscaler] Peformance issue with the autoscaler when we have ~32768 PGs added
Updated by Backport Bot 8 months ago
- Copied to Backport #62886: quincy: [pg-autoscaler] Peformance issue with the autoscaler when we have ~32768 PGs added
Updated by Backport Bot 8 months ago
- Copied to Backport #62887: pacific: [pg-autoscaler] Peformance issue with the autoscaler when we have ~32768 PGs added
Updated by Yuri Weinstein about 1 month ago
Updated by Konstantin Shalygin about 1 month ago
- Status changed from Pending Backport to Resolved
- % Done changed from 0 to 100
Actions