[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ceph-users
Subject:    [ceph-users] Re: High ceph_osd_commit_latency_ms on Toshiba MG07ACA14TE HDDs
From:       Anthony D'Atri <anthony.datri () gmail ! com>
Date:       2020-06-24 17:27:19
Message-ID: 9B69AE44-11BE-4685-92CE-2D1085240BD1 () gmail ! com
[Download RAW message or body]



> > I can remember reading this before. I was hoping you maybe had some
> > setup with systemd scripts or maybe udev.
> 
> Yeah, doing this on boot up would be ideal. I was looking really hard into tuned \
> and other services that claimed can do it, but required plugins or other stuff \
> did/does not exist and documentation is close to non-existent. 
> After spending a couple of days I gave up and went with the simple script-command \
> version. 
> If you come across something that allows easy configuration of this at boot-time, \
> please let me know.

FWIW, doing this at boot-time only doesn't address drives that are added/replaced \
without a reboot.  One could simply do so for them manually before deployment, but I \
thought I should mention it.

> I'm throwing my hat in the ring, though I know almost nothing about systemd…

In certain ways you're fortunate ;)

> Couldn't you write a script to issue the necessary commands to the desired drives, \
> then create a system unit that calls it before OSD initialization?

The systemd unit file I think accepts an ExecStartPre entry for a command to run \
before firing up the daemon, eg. /var/lib/ceph/ceph-osd-prestart.sh

> a udev rule may be easier

I'm going to pretend that you did *not* just drop the U-bomb in polite company ;)



_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-leave@ceph.io


[prev in list] [next in list] [prev in thread] [next in thread]