This is my understanding as well: as with CRUSH tunable sets, features *happen* to be named after releases don't always correlate 1:1.
On May 25, 2023, at 15:49, Wesley Dillingham <wes@wesdillingham.com> wrote:
Fairly confident this is normal. I just checked a pacific cluster and they all report luminous as well. I think some of the backstory of this is luminous is the release where up-maps were released and there hasnt been a reason to increment the features release of subsequent daemons.
To be honest I am not confident that "ceph osd set-require-min-compat-client nautilus" is a necessary step for you. What prompted you to run that command?
That step is not listed here: https://docs.ceph.com/en/latest/releases/nautilus/#upgrading-from-mimic-or-l...
but its been a bit since ive operated a pre-nautilus release.
Respectfully,
*Wes Dillingham* wes@wesdillingham.com LinkedIn <http://www.linkedin.com/in/wesleydillingham>
On Thu, May 25, 2023 at 3:14 PM Oliver Schmidt <os@flyingcircus.io> wrote:
Hi Marc,
I think for an upgrade the rocksdb is necessary. Check this for your
monitors
cat /var/lib/ceph/mon/ceph-a/kv_backend
Thanks, but I already had migrated all mons to use rocksdb when upgrading to Luminous.
~ # cat /srv/ceph/mon/ceph-host1/kv_backend rocksdb
Is this what you expect here?
Best regards Oliver _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io