On 5/07/2020 7:38 pm, Alexander E. Patrakov wrote:
If the wal location is not explicitly specified, it goes together with
the db. So it is on the SSD.
Conversely, what happens with the block.db if I place the wal with
--block.wal
The db then stays with the data.
Ah, so my 2nd reading was correct. I've recreated the OSD's on this node
3 times now :)
1. HDD Only
2. HDD + WAL on SSD
3. HDD + DB/WAL on SSD
However give the following, I see try 4 approaching...
The partition needs to be 30
or 300 GB in size (this requirement was relaxed only very recently, so
let's not count on this), but not smaller than 1-4% of the data
device.
Was not aware of that. I have two mismatched disk (500GB & 3TB) and was
allocating space proportionally.
* 25GB for the 500GB Disk
* 100GB for the 3TB Disk
But from what you are saying, the 500GB disk would have been gaining no
benefit? I would be better off allocating 30GB (or 30GB) for each disk?
* 1% for the 3TB (2.7TB effective) - RBD for VM's only.
this requirement was relaxed only very recently, so
let's not count on this
Only in master and the size can be proportional to disk size now?
Thanks!
--
Lindsay
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
