David - thanks again. Your input the last week has been invaluable.
On Wed, Aug 22, 2018 at 2:41 PM David Turner wrote:
> Yes, whatever you set your DB LV to at the time you create the Bluestore
> OSD, it will use all of that space for the db/wal. If you increase the
> size after the initial
Yes, whatever you set your DB LV to at the time you create the Bluestore
OSD, it will use all of that space for the db/wal. If you increase the
size after the initial creation, the space will not be used for the the
DB. You cannot resize it.
On Wed, Aug 22, 2018 at 3:39 PM Robert Stanford
In my case I am using the same values for lvcreate and in the ceph.conf
(bluestore* settings). Since my lvs are the size I want the db to be, and
since I'm told that the wal will live in the same place automatically, it
sounds like setting my lv to be xGB ensures Ceph will use all of this for
On Wed, Aug 22, 2018 at 2:48 PM, David Turner wrote:
> The config settings for DB and WAL size don't do anything. For journal
> sizes they would be used for creating your journal partition with ceph-disk,
> but ceph-volume does not use them for creating bluestore OSDs. You need to
> create the
The config settings for DB and WAL size don't do anything. For journal
sizes they would be used for creating your journal partition with
ceph-disk, but ceph-volume does not use them for creating bluestore OSDs.
You need to create the partitions for the DB and WAL yourself and supply
those
Hi Robert,
bluestore_allocated just tracks how many space was allocated from
slow(aka block) device to keep actual user data. It has nothing about DB
and/or WAL.
There are counters in bluefs section which track corresponding DB/WAL usage.
Thanks,
Igor
On 8/22/2018 8:34 PM, Robert
I have created new OSDs for Ceph Luminous. In my Ceph.conf I have
specified that the db size be 10GB, and the wal size be 1GB. However when
I type ceph daemon osd.0 perf dump I get: bluestore_allocated": 5963776
I think this means that the bluestore db is using the default, and not the
value
