Hi Herald,
Changing the bluestore cache settings will have no effect at all on
pglog memory consumption. You can try either reducing the number of PGs
(you might want to check and see how many PGs you have and specifically
how many PGs on that OSD), or decrease the number of pglog entries per
PG. Keep in mind that fewer PG log entries may impact recovery. FWIW,
8.5GB of memory usage for pglog implies that you have a lot of PGs per
OSD, so that's probably the first place to look.
Good luck!
Mark
On 5/12/20 5:10 PM, Harald Staub wrote:
Several OSDs of one of our clusters are down currently because RAM
usage has increased during the last days. Now it is more than we can
handle on some systems. Frequently OSDs get killed by the OOM killer.
Looking at "ceph daemon osd.$OSD_ID dump_mempools", it shows that
nearly all (about 8.5 GB) is taken by osd_pglog, e.g.
"osd_pglog": {
"items": 461859,
"bytes": 8445595868
},
We tried to reduce it, with "osd memory target" and even with
"bluestore cache autotune = false" (together with "bluestore cache
size hdd"), but there was no effect at all.
I remember the pglog_hardlimit parameter, but that is already set by
default with Nautilus I read. I.e. this is on Nautilus, 14.2.8.
Is there a way to limit this pglog memory?
Cheers
Harry
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
