Search results

Yeah, something like 960-1.2tb ssd for each node, if it fails you lose all osds in node. So yes, you could raid them up in mirror.

Yes, works okay if you need something for a remote sync.

Use enterprise disk per node and store db/wal of each hdd on it. This is the best you could get.

He wanted to make this easier for you,but there is no easy way out, i will sum his recommendations: 1) lower number of replicas - this just writes to 2 instead of 3 nodes, but this makes your cluster fragile to dying 2) use mirrored ssds for db/wal - in his case buy consumer grade to offload...

Yeah, SDDL is compatible with kernel, but kernel isnt compatible with it(GPL2).

The ceph/osd shows everything you need, so everything is okay. the hdd's have low random IOPS, and this is why when you have 70tb written to them you have low speed,and big latency. There are two options, adding db/wal onto ssd/nvme, or replace hdds with enterprise ssds.

Not necessarily, if you use ext4 local disks, or lets say hardware raid, you dont need it.

For elastic, replication doesnt get you failover, but you also get higher read speed because you are getting back results from two nodes, but in your case maybe it makes sense to set replication to 0? And of course get snapshots of indices. As always it depends on what you are storing and...

Optimal is 10g for ceph network, and for corosync, management enough is 1g.

For proxmox i would use : Samsung, Micron, Intel and probably Toshiba/Kioxia , of enterprise flavour. This is it. Of course, have backups,have redundancy and this is it.

That is also okay, maybe you didn;t study proxmox and ceph in depth to see your limits.

The filling and syncing of the disks degrades over time.

Yeah,scripts works okay, nevermind the date. It pulls from dani ,and builds .deb files. But yeah , you would need to install nginx as a reverse proxy.

Use db/wal ssds to lower a bit hdd latency. But that can fix it just a bit. Usually i would say use enterprise ssds.

Why don't you just install deb file from vaultwarden? https://github.com/greizgh/vaultwarden-debian

Corosync has an option for failover link itself, no need for active-backup: https://forum.proxmox.com/threads/configuring-dual-corosync-networks.104991/ but if management and something else is on this network,then you should separate it.

Fist question, why are you using active-backup on corosync link? As for the db/wal on faster disks read here: https://pve.proxmox.com/wiki/Deploy_Hyper-Converged_Ceph_Cluster

The latency is really high, i would add one ssd per node and more wal/db onto them.

Tell us more about ceph configuration, network, disks etc.

For now looks good with 3 clusters, testing migration :)