Re: How to (permanently) disable msgr v1 on Ceph?

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

 



> On 13-03-2025 16:08, Frédéric Nass wrote:
> > If ceph-mon respected ms_bind_msgr1 = false, then one could add --ms-bind-msgr1=false as extra_entrypoint_args in the mon service_type [1], so as to have any ceph-mon daemons deployed or redeployed using msgr v2 exclusively.
> > Unfortunately, ceph-mon doesn't respect this setting as suspected by Ilya here [2] and confirmed on a test cluster on my side. I think we can make this a tracker.
>
> Thanks for double checking, I've created [1].
> >
> > As for your other question as to when v1 will be disabled by default on new Ceph clusters, I have no idea at all.
>
> I'll leave it to the devs to discuss this one.

It would be nice if the defaults for newly created clusters also came
with the global reclaim id thing disabled, so we didn't have to
manually enable msgrv2 (and disable v1 possibly as per this thread)
and also disable the reclaim thing every time. If you upgrade an old
cluster into Reef/Squid it might also hold old clients, but newly
built ones probably won't see a lot of old clients that must have the
reclaim thing enabled, right?
_______________________________________________
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