I think the problem is that there's no MONs running now in the cluster because he upgraded them without heading the warning to update the database first. Are you suggesting he deploy new Pacific MONs using levelDB.....then update them to rocksdb after the CEPH cluster recovers? A bit confused by your response... On Mon, Oct 9, 2023 at 11:42 PM Konstantin Shalygin <k0ste@k0ste.ru> wrote:

Hi,

For this upgrade you need at least some mon's up, then you can redeploy your pacific mon's to rocksdb

k Sent from my iPhone

...

On Oct 10, 2023, at 02:01, Waywatcher <sconnary32@gmail.com> wrote:

I upgraded my CEPH cluster without properly following the mon upgrade so they were no longer on leveldb.

Proxmox and CEPH were updated to the latest for the current release. https://pve.proxmox.com/wiki/Ceph_Pacific_to_Quincy

1. The upgrade to Quincy states a recommendation that Mons are using RocksDB. 2. Leveldb support has been removed from quincy.

The monitors were still running as leveldb.

1. Does this mean the mons cannot work at all since they are levelDB?

I upgraded all nodes to the quincy release 17.2.6 and restarted the mons.

At this point the cluster stopped responding. `ceph` commands do not work since the service fails to start.

Are there steps for recovery?

1) Roll back to Pacific without being able to use CEPH commands (ceph orch upgrade start --ceph-version <version>). 2) Rebuild the monitors using data from the OSDs while maintaining Quincy release. 3) Is this actually related to the bug about 17.2.6 (which is what Proxmox/CEPH upgrades to) https://tracker.ceph.com/issues/58156 ?

I ran the upgrade on another cluster prior to this without issue. The Mons were set with RocksDB and running on Quincy 17.2.6.

I appreciate any suggestions. _______________________________________________ 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