Thanx for the advice.
We're aiming for the highest possible performance on the cluster. The
servers have 4 port 10Gbe NIC's and I have seen traffic upto about 9GB/s on
)the current single port during testing. So I want to make sure the "cache
drive" can handle the current load (9x fairly heavily
The answer tends to be “it depends”. For my test system with 144 6TB drives, I
use a 50GB DB partition. In another case of testing, we have a ratio of about
10GB per TB. What you have to watch out for is the performance difference
when the DB overruns the SSD partition.
For the WAL, I
Hi Richard,
So do you rely on the CEPH to automatically decide the WAL device's
location and size?
On Thu, Nov 23, 2017 at 4:04 PM, Richard Hesketh <
richard.hesk...@rd.bbc.co.uk> wrote:
> Keep in mind that as yet we don't really have good estimates for how large
> bluestore metadata DBs may
Aah, ok. That makes sense. For what it's worth, I'm using Proxmox and
Proxmox doesn't seem to create the WAL, only the DB, hence the command I
used to specifically create them both.
On Thu, Nov 23, 2017 at 6:16 PM, Richard Hesketh <
richard.hesk...@rd.bbc.co.uk> wrote:
> On 23/11/17 16:13, Rudi
On 23/11/17 16:13, Rudi Ahlers wrote:
> Hi Caspar,
>
> Thanx. I don't see any mention that it's a bad idea to have the WAL and DB on
> the same SSD, but I guess it could improve performance?
It's not that it's a bad idea to put WAL and DB on the same device - it's that
if not otherwise
Hi Caspar,
Thanx. I don't see any mention that it's a bad idea to have the WAL and DB
on the same SSD, but I guess it could improve performance?
I do understand that if I loose the the WAL drive, I loose the OSD's as
well.
>From what I gather, I can't move the WAL or DB devices and would have
Keep in mind that as yet we don't really have good estimates for how large
bluestore metadata DBs may become, but it will be somewhat proportional to your
number of objects. Considering the size of your OSDs, a 15GB block.db partition
is almost certainly too small. Unless you've got a
Rudi,
First off all do not deploy an OSD specifying the same seperate device for
DB and WAL:
Please read the following why:
http://docs.ceph.com/docs/master/rados/configuration/bluestore-config-ref/
That said you have a fairly large amount of SSD size available so i
recommend using it as
When I look at the drive partitions the DB / WAL partitions are
only 576Mb & 1GB respectively. This feels a bit small.
Before deploy bluestore OSD you should define your db/wal size via:
ceph_bluestore_block_db_size: '32212254720' # 30Gb
ceph_bluestore_block_wal_size: '1073741824' # 1Gb
Hi,
Can someone please explain this to me in layman's terms. How big a WAL
drive do I really need?
I have a 2x 400GB SSD drives used as WAL / DB drive and 4x 8TB HDD's used
as OSD's. When I look at the drive partitions the DB / WAL partitions are
only 576Mb & 1GB respectively. This feels a bit
10 matches
Mail list logo
