Balancer vs. Autoscaler

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

 



Hi everyone,

I had the autoscale_mode set to "on" and the autoscaler went to work and
started adjusting the number of PGs in that pool. Since this implies a
huge shift in data, the reweights that the balancer had carefully
adjusted (in crush-compat mode) are now rubbish, and more and more OSDs
become nearful (we sadly have very different sized OSDs).

Now apparently both manager modules, balancer and pg_autoscaler, have
the same threshold for operation, namely target_max_misplaced_ratio. So
the balancer won't become active as long as the pg_autoscaler is still
adjusting the number of PGs.

I already set the autoscale_mode to "warn" on all pools, but apparently
the autoscaler is determined to finish what it started.

Is there any way to pause the autoscaler so the balancer has a chance of
fixing the reweights? Because even in manual mode (ceph balancer
optimize), the balancer won't compute a plan when the misplaced ratio is
higher than target_max_misplaced_ratio.

I know about "ceph osd reweight-*", but they adjust the reweights
(visible in "ceph osd tree"), whereas the balancer adjusts the "compat
weight-set", which I don't know how to convert back to the old-style
reweights.

Best regards,
Jan-Philipp
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



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


  Powered by Linux