Discussion:
[ceph-users] Sizing for bluestore db and wal
Felix Stolte
2018-11-26 09:09:55 UTC
Permalink
Hi folks,

i upgraded our ceph cluster from jewel to luminous and want to migrate
from filestore to bluestore. Currently we use one SSD as journal for
thre 8TB Sata Drives with a journal partition size of 40GB. If my
understanding of the bluestore documentation is correct, i can use a wal
partition for the writeahead log (to decrease write latency, similar to
filestore) and a db partition for metadata (decreasing write AND read
latency/throughput). Now I have two questions:

a) Do I really need an WAL partition if both wal and db are on the same SSD?

b) If so, what would the ratio look like? 99% db, 1% wal?


Best regards, Felix
--
Forschungszentrum JÃŒlich GmbH
52425 JÃŒlich
Sitz der Gesellschaft: JÃŒlich
Eingetragen im Handelsregister des Amtsgerichts DÃŒren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir. Dr. Karl Eugen Huthmacher
GeschÀftsfÌhrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
Janne Johansson
2018-11-26 09:27:56 UTC
Permalink
Post by Felix Stolte
Hi folks,
i upgraded our ceph cluster from jewel to luminous and want to migrate
from filestore to bluestore. Currently we use one SSD as journal for
thre 8TB Sata Drives with a journal partition size of 40GB. If my
understanding of the bluestore documentation is correct, i can use a wal
partition for the writeahead log (to decrease write latency, similar to
filestore) and a db partition for metadata (decreasing write AND read
a) Do I really need an WAL partition if both wal and db are on the same SSD?
I think the answer is no here, if you point the DB to an SSD, bluestore will
use it for WAL also.
Post by Felix Stolte
b) If so, what would the ratio look like? 99% db, 1% wal?
..which means just let ceph handle this itself.
--
May the most significant bit of your life be positive.
Loading...