That's indeed the case:
# ceph config get osd osd_op_queue
mclock_scheduler
Thank you very much for this tip, I'll play with mclock parameters.
On 05/10/22 13:11, Janne Johansson wrote:
# ceph tell osd.2 config get osd_max_backfills
{
"osd_max_backfills": "1000"
}
makes little sense to
On 10/5/22 12:09, Nicola Mori wrote:
Dear Ceph users,
I am trying to tune my cluster's recovery and backfill. On the web I
found that I can set related tunables by e.g.:
ceph tell osd.* injectargs --osd-recovery-sleep-hdd=0.0
--osd-max-backfills=8 --osd-recovery-max-active=8
: ceph-users@ceph.io
Onderwerp: [ceph-users] Re: ceph tell setting ignored?
But how can I check if the applied temporary value has been correctly set?
Maybe I'm doing something wrong, but this:
# ceph tell osd.2 config set osd_max_backfills 8 {
"success": "osd_max_backfills =
> # ceph tell osd.2 config get osd_max_backfills
> {
> "osd_max_backfills": "1000"
> }
>
> makes little sense to me.
This means you have the mClock IO scheduler, and it gives back this
value since you are meant to change the mClock priorities and not the
number of backfills.
Some more info
But how can I check if the applied temporary value has been correctly
set? Maybe I'm doing something wrong, but this:
# ceph tell osd.2 config set osd_max_backfills 8
{
"success": "osd_max_backfills = '8' "
}
# ceph tell osd.2 config get osd_max_backfills
{
"osd_max_backfills": "1000"
}
Injection modifies the running state of the specified daemons. It does not
modify the central config database (saved / persistent state). Injected values
will go away when the daemon restarts.
> On Oct 5, 2022, at 6:10 AM, Nicola Mori wrote:
>
> Dear Ceph users,
>
> I am trying to tune
