It is true, on the slide it was understood to use this configuration. Thanks
for the answer.
Em sex., 26 de mar. de 2021 às 10:26, Szabo, Istvan (Agoda) <
Istvan.Szabo(a)agoda.com> escreveu:
Makes sense what you are talking about, I had the same
confusing like you,
finally went with redhat setup:
https://hubb.blob.core.windows.net/c2511cea-81c5-4386-8731-cc444ff806df-pub…
Slide 27.
Istvan Szabo
Senior Infrastructure Engineer
---------------------------------------------------
Agoda Services Co., Ltd.
e: istvan.szabo(a)agoda.com
---------------------------------------------------
-----Original Message-----
From: Marcelo <raxidex(a)gmail.com>
Sent: Friday, March 26, 2021 7:35 PM
Cc: ceph-users(a)ceph.io
Subject: [Suspicious newsletter] [ceph-users] Re: [Suspicious newsletter]
bucket index and WAL/DB
This is exactly the problem, so we thought about not risking losing the
entire host by using both NVMes.
From what I understand the bucket index data is stored in the omap, which
is stored in the block.db, making it unnecessary to create a separate OSD
for the bucket index. But I didn't find anything in the documentation about
it.
It is also unclear whether, if it is necessary to create a separate index
pool, it would be recommended to place the OSD that serves that pool with
wal / DB.
Em qui., 25 de mar. de 2021 às 22:42, Szabo, Istvan (Agoda) <
Istvan.Szabo(a)agoda.com> escreveu:
In couple of documentation that I've read I
finally made the decision
to separate index from wal+db.
However don't you think that the density is a bit high with 12HDD for
1 nvme? So if you loose nvme you actually loose your complete host and
a lot of data movements will happen.
Istvan Szabo
Senior Infrastructure Engineer
---------------------------------------------------
Agoda Services Co., Ltd.
e: istvan.szabo(a)agoda.com
---------------------------------------------------
-----Original Message-----
From: Marcelo <raxidex(a)gmail.com>
Sent: Thursday, March 25, 2021 11:15 PM
To: ceph-users(a)ceph.io
Subject: [Suspicious newsletter] [ceph-users] bucket index and WAL/DB
Hello everybody.
I searched in several places and I couldn't find any information about
what the best bucket index and WAL / DB organization would be.
I have several hosts consisting of 12 HDDs and 2 NVMes, and currently
one of the NVMes serves as WAL / DB for the 10 OSDs and the other NVMe
is partitioned in two, serving as 2 OSDs to serve the S3 index pool.
I saw in ceph-ansible a playbook (infrastructure-playbooks /
lv-create.yml) that creates a division where we have an OSD living
with a journal on the same NVMe. The problem is that in lv-vars.yaml
used by lv-create.yml it is said that this only applies to the
filestore. Is this correct or can I use this same structure with
bluestore?
Thank you all,
Marcelo.
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io To unsubscribe send an
email to ceph-users-leave(a)ceph.io
________________________________
This message is confidential and is for the sole use of the intended
recipient(s). It may also be privileged or otherwise protected by
copyright or other legal rules. If you have received it by mistake
please let us know by reply email and delete it from your system. It
is prohibited to copy this message or disclose its content to anyone.
Any confidentiality or privilege is not waived or lost by any mistaken
delivery or unauthorized disclosure of the message. All messages sent
to and from Agoda may be monitored to ensure compliance with company
policies, to protect the company's interests and to remove potential
malware. Electronic messages may be intercepted, amended, lost or
deleted, or
contain viruses.
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io To unsubscribe send an
email to ceph-users-leave(a)ceph.io
________________________________
This message is confidential and is for the sole use of the intended
recipient(s). It may also be privileged or otherwise protected by copyright
or other legal rules. If you have received it by mistake please let us know
by reply email and delete it from your system. It is prohibited to copy
this message or disclose its content to anyone. Any confidentiality or
privilege is not waived or lost by any mistaken delivery or unauthorized
disclosure of the message. All messages sent to and from Agoda may be
monitored to ensure compliance with company policies, to protect the
company's interests and to remove potential malware. Electronic messages
may be intercepted, amended, lost or deleted, or contain viruses.