>> You don’t strictly need an admin node as such. Only worry about clock rate
>> if you’re doing CephFS.
> So an admin node is not required?
It isn’t. An admin node basically is any system with the admin keys installed.
With production clusters there can be some advantages to having one,
Hi, thanks for your answers!
On mån, jan 1 2024 at 17:00:59 -0500, Anthony D'Atri
wrote:
Hi and thanks for your answers!
So my understanding from this, make sure that the "admin" node
have a fast CPU
You don’t strictly need an admin node as such. Only worry about
clock rate if
> Hi and thanks for your answers!
>
> So my understanding from this, make sure that the "admin" node
> have a fast CPU
You don’t strictly need an admin node as such. Only worry about clock rate if
you’re doing CephFS.
>max = 3 and min = 2.
For your pools, size=3, min_size=2. These are
Hi and thanks for your answers!
So my understanding from this,
make sure that the "admin" node
have a fast CPU and the minimum
data nodes for production is three
and max = 3 and min = 2.
You can expand this cluster
by just adding one data node,
there is no need to expand with
another 3 nodes,
>>
>> You can do that for a PoC, but that's a bad idea for any production
>> workload. You'd want at least three nodes with OSDs to use the default RF=3
>> replication. You can do RF=2, but at the peril of your mortal data.
>
> I'm not sure I agree - I think size=2, min_size=2 is no worse
Disclaimer: I'm fairly new to Ceph, but I've read a bunch of threads
on the min_size=1 issue as that was perplexing me when I started, as
one replica is generally considered fine in many other applications.
However, there really are some unique concerns to Ceph beyond just the
number of disks you
> I have manually configured a ceph cluster with ceph fs on debian bookworm.
Bookworm support is very, very recent I think.
> What is the difference from installing with cephadm compared to manuall
> install,
> any benefits that you miss with manual install?
A manual install is dramatically
