Re: BlueStore sizing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



It will automatically spill over to the slower storage if necessary;
it's better to have some fast storage for the DB than just slow
storage.


Paul

2018-08-20 13:07 GMT+02:00 Harald Staub <harald.staub@xxxxxxxxx>:
> As mentioned here recently, the sizing recommendations for BlueStore have
> been updated:
> http://docs.ceph.com/docs/master/rados/configuration/bluestore-config-ref/#sizing
>
> In our ceph cluster, we have some ratios that are much lower, like 20GB of
> SSD (WAL and DB) per 7TB of spinning space. This stems from the fact that it
> started much earlier, with sizing done with filestore based OSDs in mind
> (SSDs for journals), that were converted to BlueStore later.
>
> So SSD space is much lower than recommended, but much higher than needed for
> WAL only. Would it still be better to remove the DB from SSD? Or what
> problems could arise with our current setup? Up to now (several months), we
> do not see any disadvantages.
>
>  Harry
> _______________________________________________
> ceph-users mailing list
> ceph-users@xxxxxxxxxxxxxx
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



-- 
Paul Emmerich

Looking for help with your Ceph cluster? Contact us at https://croit.io

croit GmbH
Freseniusstr. 31h
81247 München
www.croit.io
Tel: +49 89 1896585 90
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux