Feature #8695
OSD: make osd_backfill_full_ratio respond to injectargs/whatever
0%
Description
Right now, it's just set up on boot up, but obviously there's interest in it being something you can change at runtime.
Related issues
History
#1 Updated by Haomai Wang over 9 years ago
I have another concern, how to know the option can be changed on runtime without viewing source?
#2 Updated by Sage Weil over 9 years ago
We had a discussion about revamping the config stuff during the giant CDS to address that; see
http://wiki.ceph.com/Planning/Blueprints/Giant/annotate_config_options
http://pad.ceph.com/p/cdsgiant-annotate-config-perfcounters
http://www.youtube.com/watch?v=bQuGZ-3u8Xw&feature=share&t=3m58s
#3 Updated by Greg Farnum over 9 years ago
Okay, this value actually does respond to injectargs (it's re-read every time it's used), but I'm under the impression that if you change the value while all the PGs are in the backfill_toofull state, nothing will wake them up.
#4 Updated by Laurent GUERBY over 8 years ago
We had backfill_toofull on one of our 0.94.5 OSD and we did
ceph tell osd.* injectargs '--osd-backfill-full-ratio 0.99'
It solved the stuck recovery immediately but a warning continue to appear in the OSD logs:
2015-11-17 09:15:04.114387 7f3965fd8700 0 log_channel(cluster) log [WRN] : OSD near full (90%)
It would be nice on those "full" warning to know which "full" knob is at play:
osd_backfill_full_ratio = 0.99
mon_osd_nearfull_ratio = 0.98
mon_osd_full_ratio = 0.99
#5 Updated by Loïc Dachary over 8 years ago
- Related to Documentation #13814: document the *_full* config options added
#6 Updated by Patrick Donnelly about 5 years ago
- Project changed from Ceph to RADOS
- Category deleted (
OSD) - Start date deleted (
06/30/2014) - Component(RADOS) OSD added