Hi Sage, I tested again with setting paxos_propose_interval = 0.3 Now stopping OSDs causes way less slow ops. While starting OSDs the slows seems gone. With osd_fast_shutdown_notify_mon = true the slow ops are gone completely. So I would like to keep the shutdown notify enabled. As far as I understand the paxos propose interval. This is the interval in which messages are processed and leads, if neccessary, to new OSDMaps. Correct? I wonder if a smaller value could lead to load issues on bigger clusters while some impact happens, like a host or a whole rack goes down. Thanks Manuel On Thu, 4 Nov 2021 17:51:55 -0500 Sage Weil <sage@xxxxxxxxxxxx> wrote: > Can you try setting paxos_propose_interval to a smaller number, > like .3 (by default it is 2 seconds) and see if that has any effect. > > It sounds like the problem is not related to getting the OSD marked > down (or at least that is not the only thing going on). My next > guess is that the peering process that follows needs to get OSDs' > up_thru values to update and there is delay there. > > Thanks! > sage > > > On Thu, Nov 4, 2021 at 4:15 AM Manuel Lausch <manuel.lausch@xxxxxxxx> > wrote: > > > On Tue, 2 Nov 2021 09:02:31 -0500 > > Sage Weil <sage@xxxxxxxxxxxx> wrote: > > > > > > > > > > Just to be clear, you should try > > > osd_fast_shutdown = true > > > osd_fast_shutdown_notify_mon = false > > > > I added some logs to the tracker ticket with this options set. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |