Dillingham
Cc: ceph-users@ceph.io; a...@dreamsnake.net
Subject: [ceph-users] Re: `ceph features` on Nautilus still reports "luminous"
> To be honest I am not confident that "ceph osd set-require-min-compat-client
> nautilus" is a necessary step for you. What prompt
> 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-luminous
You're
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 wrote:
>
> Fairly confident this is normal. I just checked a pacific cluster and they
> all report luminous as
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
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
>
> on our way towards getting our cluster to a current Ceph release, we
> updated all hosts and clients to Nautilus 14.2.22.
I think for an upgrade the rocksdb is necessary. Check this for your monitors
cat /var/lib/ceph/mon/ceph-a/kv_backend
___
