Search results

This is why I recommend a minimum of 5 nodes for Ceph.

Just the rule does not matter if there is no pool using the rule. You could re-configure all your pools to use the first rule "replicated_rule" when you only have the same type of SSDs in the cluster, but it may cause some backfilling traffic. After that you could remove both rules that...

You would need to have 5 nodes with Ceph OSDs to sustain 2 failed nodes. And even then they should not fail at the same time.

Das klingt aber nach einem Bug, oder? Denn warum sollte in dem Feld nicht der aktuelle Wert angezeigt werden?

Even with a cephadm orchestrated cluster the NVMe-oF feature is currently not production ready. The documentation is ahead of the released code here.

You cannot failover in a WAN setup with VPN. The latencies are too high to setup a HA cluster.

Du hast auch nur zwei OSDs in der Device-Class "large_ssd". Wie soll das funktionieren?

Because that's a single client. As you see with multiple clients performance scales up well.

Sorry, sometimes the Ceph documentation describes features that have not been released yet.

I would replace "firstn 3" with "firstn 0" to make the rules more generic. I do not if it's possible to remove the global stretch mode from a cluster. Maybe you should ask on the Ceph mailing list.

You have enabled stretch mode for the whole cluster. This means that all PGs from all pools need to be distributed across both DCs before they become active. Quoting the docs https://docs.ceph.com/en/squid/rados/operations/stretch-mode/ : What your want can be achieved with enabling stretch...

Sinn und Zweck der Routing-Protokolle ist es, eigentlich immer den kürzesten bzw "billigsten" Weg durchs Netz zu finden. Das was Du erreichen möchtest ist soweit ich weiß einfach nicht möglich.

Ceph Squid is still a point zero release (19.2.0). That's maybe why it's not recommended.

IMHO this would be easier in that situation than trying to play catch with changing CDN IPs.

Single thread performance like you have with one disk inside one VM will always be disappointing, especially with small block sizes. You can just throw faster hardware at the problem. BTW: Your rados bench uses 16 parallel threads and a block size of 4MB. This will show you nearly the maximum...

Have you added 'images' in the storage config forCephFS? After importing the image you still can migrate it to the RBD pool. Or select the target storage in the import dialog.

Get multiple OSDs per node and 25G network. You are running the bare minimum for a working system.

Usually bonding is used with LACP and a corresponding switch stack to provide network redundancy. As Ceph uses multiple TCP connections both physical links are utilized.

It is compatible with RBD and qcow2.

Es muss kein aufwendiges shared Storage dranhängen, um den Fehler zu reproduzieren. Ich habe die notwendigen Schritte hier dokumentiert: http://gurubert.de/ocfs2_io_uring.html