Re: mon_osd_nearfull_ratio (unchangeable) ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

On Tue, 26 Jul 2016 12:16:35 +1000 Goncalo Borges wrote:

> Hi Brad
> 
> Thanks for replying.
> 
> Answers inline.
> 
> 
> >> I am a bit confused about the 'unchachable' message we get in Jewel 10.2.2
> >> when I try to change some cluster configs.
> >>
> >> For example:
> >>
> >> 1./ if I try to change mon_osd_nearfull_ratio from 0.85 to 0.90, I get
> >>
> >>     # ceph tell mon.* injectargs "--mon_osd_nearfull_ratio 0.90"
> >>     mon.rccephmon1: injectargs:mon_osd_nearfull_ratio = '0.9'
> >>     (unchangeable)
> >>     mon.rccephmon3: injectargs:mon_osd_nearfull_ratio = '0.9'
> >>     (unchangeable)
> >>     mon.rccephmon2: injectargs:mon_osd_nearfull_ratio = '0.9'
> >>     (unchangeable)
> > This is telling you that this variable has no observers (i.e. nothing monitors
> > it dynamically) so changing it at runtime has no effect. IOW it is read at
> > start-up and not referred to again after that IIUC.
> >
> >> but the 0.85 default values continues to be showed in
> >>
> >>      ceph --show-config --conf /dev/null | grep mon_osd_nearfull_ratio
> >>      mon_osd_nearfull_ratio = 0.85
> > Try something like the following.
> >
> > $ ceph daemon mon.a config show|grep mon_osd_nearfull_ratio
> >
> >> and I continue to have health warnings regarding near full osds.
> > So the actual config value has been changed but has no affect and will not
> > persist. IOW, this value needs to be modified in the conf file and the daemon
> > restarted.
> >
> >>
> >> 2./ If I change in the ceph.conf and restart services, I get the same
> >> behaviour as in 1./ However, if I check the daemon configuration, I see:
> > Please clarify what you mean by "the same behaviour"?
> 
> So, in my ceph.conf I've set 'mon osd nearfull ratio = 0.90' and 
> restarted mon and osd (not sure if those were needed) daemons everywhere.
> 
> After restarting, I am still getting the health warnings regarding near 
> full osds above 85%. If the new value was active, I should not get such 
> warnings.
> 
> >
> >>      # ceph daemon mon.rccephmon2 config show | grep mon_osd_nearfull_ratio
> >>      "mon_osd_nearfull_ratio": "0.9",
> > Use the daemon command I showed above.
> 
> Isn't it the same as you suggested? That was run after restarting 
> services so it is still unclear to me why the new value is not picked up 
> and why running 'ceph --show-config --conf /dev/null | grep 
> mon_osd_nearfull_ratio' still shows 0.85
> 
Don't use that, do something like:

ceph --admin-daemon /var/run/ceph/ceph-mon.<hostname>.asok config show |grep full

to get running values (on a MON host obviously).

> Maybe a restart if services is not what has to be done but a stop/start 
> instead?
>
Restart should be be OK, but then again with all systemd transition fun,
who knows.
 
Christian
> Cheers
> Goncalo
> _______________________________________________
> ceph-users mailing list
> ceph-users@xxxxxxxxxxxxxx
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> 


-- 
Christian Balzer        Network/Systems Engineer                
chibi@xxxxxxx   	Global OnLine Japan/Rakuten Communications
http://www.gol.com/
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux