Hi,
what is the purpose of the db_slots attribute in a DriveGroup specification?
My interpretation of the documentation is that I can define how many
OSDs use one db device.
https://docs.ceph.com/en/reef/cephadm/services/osd/#additional-options
"db_slots - How many OSDs per DB device"
The default for the cephadm orchestrator is to create as many DB volumes
on a DB device as needed for the number of OSDs.
In a scenario where there are empty slots for HDDs and an existing DB
device should not be used fully "db_slots" could be used.
But even if db_slots is in an OSD service spec the orchestrator will
only create as many DB volumes as there are HDDs currently available.
There is a discussion from 2021 where the use of "block_db_size" and
"limit" is suggested:
https://lists.ceph.io/hyperkitty/list/ceph-users@xxxxxxx/thread/6EVOYOHS3BTTNLKBRGLPTZ76HPNLP6FC/#6EVOYOHS3BTTNLKBRGLPTZ76HPNLP6FC
Shouldn't db_slots make that easier?
Is this a bug in the orchestrator?
Regards
--
Robert Sander
Heinlein Consulting GmbH
Schwedter Str. 8/9b, 10119 Berlin
http://www.heinlein-support.de
Tel: 030 / 405051-43
Fax: 030 / 405051-19
Zwangsangaben lt. §35a GmbHG:
HRB 220009 B / Amtsgericht Berlin-Charlottenburg,
Geschäftsführer: Peer Heinlein -- Sitz: Berlin
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
