Hi,
So it seems we're still on leveldb. We're using ceph through our proxmox
cluster, and we're on 14.2.22.
We know we have some upgrading to do, and we expect that the excellent
pve upgrade wiki will (as usual) inform us how to upgrade including
leveldb to rocksdb.
(even though at this moment, we don't find much info on converting from
leveldb to rocksdb on the pve wiki)
MJ
Op 15-10-2021 om 09:30 schreef Dan van der Ster:
For a mon:
# cat /var/lib/ceph/mon/ceph-xxx/kv_backend
rocksdb
For an OSD, look for leveldb/rocksdb messages in the log.
-- dan
On Fri, Oct 15, 2021 at 9:14 AM mj <lists@xxxxxxxxxxxxx> wrote:
This is a very basic question, but how to quickly check if you still run
levelbd instead of rocksdb?
Op 14-10-2021 om 16:55 schreef Konstantin Shalygin:
+1 we convert all levelbd monstore to rocksdb on luminous
k
Sent from my iPhone
On 14 Oct 2021, at 10:42, Dan van der Ster <dan@xxxxxxxxxxxxxx> wrote:
+1 from users perspective too but we should warn add a HEALTH_WARN if
a cluster has leveldb monstore or filestore osds, so users know to
convert before upgrading.
-- dan
On Wed, Oct 13, 2021 at 8:39 PM Casey Bodley <cbodley@xxxxxxxxxx> wrote:
+1 from a dev's perspective. we don't test leveldb, and we don't
expect it to perform as well as rocksdb in ceph, so i don't see any
value in keeping it
the rados team put a ton of effort into converting existing clusters
to rocksdb, so i would be very surprised if removing leveldb left any
users stuck without an upgrade path
On Wed, Oct 13, 2021 at 2:13 PM Ken Dreyer <kdreyer@xxxxxxxxxx> wrote:
I think it's a great idea to remove it.
- Ken
On Wed, Oct 13, 2021 at 12:52 PM Adam C. Emerson <aemerson@xxxxxxxxxx> wrote:
Good day,
Some time ago, the LevelDB maintainers turned -fno-rtti on in their
build. As we don't use -fno-rtti, building LevelDBStore
against newer LevelDB packages can fail.
This has made me wonder, are there still people who use LevelDBStore
and rely on it, or can we deprecate and/or remove it?
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx