The idea is to avoid separate WAL partition - it doesn't make sense for
single NVMe device - just compicates things.
And if you don't specify WAL explicitly it's co-exist with DB.
Hence I vote for the second option :)
On 6/29/2018 12:07 AM, Kai Wagner wrote:
I'm also not 100% sure but I
On 28.06.2018 23:25, Eric Jackson wrote:
> Recently, I learned that this is not necessary when both are on the same
> device. The wal for the Bluestore OSD will use the db device when set to 0.
That's good to know. Thanks for the input on this Eric.
--
SUSE Linux GmbH, GF: Felix Imendörffer,
I'm going to hope that Igor is correct since I have a PR for DeepSea to change
this exact behavior.
With respect to ceph-deploy, if you specify --block-wal, your OSD will have a
block.wal symlink. Likewise, --block-db will give you a block.db symlink.
If you have both on the command line, you
I'm also not 100% sure but I think that the first one is the right way
to go. The second command only specifies the db partition but no
dedicated WAL partition. The first one should do the trick.
On 28.06.2018 22:58, Igor Fedotov wrote:
>
> I think the second variant is what you need. But I'm
I think the second variant is what you need. But I'm not the guru in
ceph-deploy so there might be some nuances there...
Anyway the general idea is to have just a single NVME partition (for
both WAL and DB) per OSD.
Thanks,
Igor
On 6/27/2018 11:28 PM, Pardhiv Karri wrote:
Thank you Igor
Hi Pardhiv,
there is no WalDB in Ceph.
It's WAL (Write Ahead Log) that is a way to ensure write safety in
RocksDB. In other words - that's just a RocksDB subsystem which can use
separate volume though.
In general For BlueStore/BlueFS one can either allocate separate volumes
for WAL and DB
