Actions
Bug #58642
openNo way to recover when set hit_set_count to very large number
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Description
When set hit_set_count to very large number(in my case 1234567890),
OSD starts consuming a lot of memory and killed by OOM.
and it repeats even when the OSD is restarted.
The problem is that setting hit_set_count back to 0 or removing the pool doesn't solve the problem.
Even removing that pool and OSDs and deploying a new OSD will still cause problems.
No data to display
Actions