Thank you for the detailed answer. I'll buy more RAM for the machine.
Nicola
On 03/10/22 10:02, Janne Johansson wrote:
There is definitely something wrong in how my cluster manages
osd_memory_target. For example, this is the situation for OSD 16:
The memory limit seems to be correctly set (I disabled the memory
autotune on the host, set the limit manually with --force and rebooted
the host) but nevertheless the actual memory usage is far above the
limit (568M vs 384M).
The memory target (and <1G is too small by far) is only directing the
things that *can* be tuned, there are other things the OSD needs
memory for which are not optional and those will take memory even if
you set the limits to X GB. Also, while you may find some lower limit
that works in some fashion, later events such as
rebalancing,recovery,backfills and upstart-checks *will* need more
memory even if only temporarily.
What you are setting is more or less like setting the autopilot engine
level on an airplane at the cruising altitude, it does *not* control
how much engine is needed for take-off, landings or emergencies.
--
Nicola Mori, Ph.D.
INFN sezione di Firenze
Via Bruno Rossi 1, 50019 Sesto F.no (Italy)
+390554572660
mori@xxxxxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
