Re: High usage (DATA column) on dedicated for OMAP only OSDs

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

 



Hi,

> On 19 Sep 2024, at 18:26, Joshua Baergen <jbaergen@xxxxxxxxxxxxxxxx> wrote:
> 
> Whenever we've seen osdmaps not being trimmed, we've made sure that
> any down OSDs are out+destroyed, and then have rolled a restart
> through the mons. As of recent Pacific at least this seems to have
> reliably gotten us out of this situation.

This helps for a years. For the mons. But sometimes not for the OSD
Alex, I suggest to you - use pgremapper for cancel-backfill. Then see for OSD status - maps is prune or not
In case, when everything is clean, but maps are not prune - I issued new osdmaps via setting and then unsetting osd flags (noout, for example). After each new map, by default OSD should prune 30 old osdmaps

P.S.: Am I right in understanding that the OSD deletes the old osdmaps (prune) only if a new one is issued (as trigger)?


k
_______________________________________________
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