Actions
Bug #5298
openmon: "setting" CRUSH tunables to their current values creates a map
Status:
New
Priority:
Low
Assignee:
-
Category:
Performance/Resource Usage
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Monitor
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Maybe this is adding pointless churn, maybe it's blocking the user longer than necessary, or maybe it's a great way to poke the OSDMap that we don't want to fix. But I noticed this and our other ops tend to return when setting something to its current status.
Updated by Greg Farnum almost 7 years ago
- Project changed from Ceph to RADOS
- Category changed from Monitor to Performance/Resource Usage
- Component(RADOS) Monitor added
Actions