Re: The effect of changing an osd's class

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

 



How do I determine the primary osd?

On 2024/11/14 16:12, Anthony D'Atri wrote:
You might also first try

		ceph osd down 1701

This marks the OSD down in the map, it doesn’t restart anything, but it does serve in some cases to goose progress.  The OSD will quickly mark itself back up.

Where 1701 is the ID of said primary.

		ceph health detail

is one way that you might see the acting sets of involved PGs, the primary will be the first ID in each’s list.  Chances are that you’ll see a common OSD in the sets.

On Nov 14, 2024, at 8:22 AM, Frédéric Nass <frederic.nass@xxxxxxxxxxxxxxxx> wrote:

One think I can think of is that these 113 PGs may have a common misbehaving OSD (primary or not) with a ridiculous osd_mclock_max_capacity_iops_ssd value set.
Restarting the primary and/or adjusting osd_mclock_max_capacity_iops_ssd value(s) could help in this situation.
_______________________________________________
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




[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