Actions
Bug #24685
closedconfig options: possible inconsistency between flag 'can_update_at_runtime' and 'flags' list
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
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
I'm wondering if there is a inconsistency between the 'can_update_at_runtime' flag and the 'flags' list for the config options.
E.g. 'ceph config help bluestore_compression_required_ratio --format=json-pretty' returns:
{
"name": "bluestore_compression_required_ratio",
"type": "double",
"level": "advanced",
"desc": "Compression ratio required to store compressed data",
"long_desc": "If we compress data and get less than this we discard the result and store the original uncompressed data.",
"default": 0.875000,
"daemon_default": "",
"tags": [],
"services": [],
"see_also": [],
"min": "",
"max": "",
"can_update_at_runtime": true,
"flags": [
"runtime"
]
}
Which is correct from my point of view. But 'ceph config help bluestore_compression_required_ratio --format=json-pretty' returns:
{
"name": "bluestore_cache_trim_max_skip_pinned",
"type": "uint64_t",
"level": "dev",
"desc": "Max pinned cache entries we consider before giving up",
"long_desc": "",
"default": 64,
"daemon_default": "",
"tags": [],
"services": [],
"see_also": [],
"min": "",
"max": "",
"can_update_at_runtime": true,
"flags": []
}
As you can see 'can_update_at_runtime' is 'true' but 'runtime' is missing in the 'flags' list.
Actions