gurubert's latest activity
-
gurubert replied to the thread Ceph Squid (19.2.3) Cluster Hangs on Node Reboot - 56 NVMe OSDs - PVE 9.1.1.Is a specific pool affected by shutting down one host? Your CRUSH rules are a wild mix. -
...all right - that is super embarassing - the sfp+ module for ceph public network was not entierly plugged in -> network connectivity missing ...
-
gurubert replied to the thread Ceph Squid (19.2.3) Cluster Hangs on Node Reboot - 56 NVMe OSDs - PVE 9.1.1.Please post the output of ceph status ceph mon dump ceph config dump ceph osd df tree ceph osd crush rule dump ceph osd pool ls detail from each node: ip addr show
-
Klar bremst der RAID Controller. Ich würde nie NVMe hinter einen RAID Controller packen. Die RAID Controller haben in der Regel 8 PCI Lanes und jede NVMe auch schon 4, somit ist der RAID Controller immer ein Bottleneck bei mehr als 2 NVMe. Dann...
-
Ganz klar, die falsche CPU im Host gewählt. Das Backup führt der Proxmox Backup Client aus auf dem PVE. Dieser muss die Daten auch Komprimieren, was von der Single Core Performance des Hosts abhängt. Da die CPU nur 525MB/s Compression schafft und...
-
gurubert reacted to Chris's post in the thread How to Do incremental Restore using Proxmox Backup server 3.4.0 with
Like.
You might be able to achieve what you want using the single file restore feature, which allows to download parts of the filesystem of a VM as zip or tar archive. You will however have to copy and place the files into your VM manually, there is... -
Should work. I have it running here too. Here is an additional current link for part of it. https://docs.checkmk.com/latest/en/monitoring_proxmox.html
-
16 consumer NVMe drives. Any write Ceph does is sync and any drive without PLP will show high latency and, once its cache fills, poor sequential performance. Keep in mind that you have to write to 3 disks and besides data itself it has to write...
-
gurubert reacted to Falk R.'s post in the thread Ceph Performance Problem trotz guter Ceph Benchmarks with Like.
Write Back, schreibt immer erst einmal in den RAM. Der Ceph Benchmark macht immer mehrere Streams. Dein Diskmark nur einen auf einer vDisk. Mehrere VMs performen dann auch schön. Produktiv habe ich nirgends Performanceprobleme, auch nicht bei...
-
gurubert reacted to SteveITS's post in the thread Ceph Performance Problem trotz guter Ceph Benchmarks with Like.
Try using CPU x86-64-v2-AES or x86-64-v3-AES instead of "host." Google Translate: Versuchen Sie, anstelle von „host“ die CPU-Typen x86-64-v2-AES oder x86-64-v3-AES zu verwenden...
-
A status update on this: Two corosync parameters that are especially relevant for larger clusters are the "token timeout" and the "consensus timeout". When a node goes offline, corosync (or rather the totem protocol it implements) will need to...
-
gurubert reacted to fstrankowski's post in the thread Ceph Performance Problem trotz guter Ceph Benchmarks with Like.
Kannst Du bitte mal dein Setup genauer beschreiben. ceph osd df tree qm config <VMID> ceph osd pool ls detail ceph osd pool autoscale-status Bitte setze dein Output immer in [ CODE ] tags (oben im Menü das "</>"), dann kann man das deutlich...
-
gurubert replied to the thread Ceph Performance Problem trotz guter Ceph Benchmarks.Die Windows-VM benutzt virtio-scsi-single?
-
gurubert reacted to Eduardo Taboada's post in the thread CEPH Probleme : 2 OSD(s) have spurious read errors with Like.
Is a good practice to separate Ceph data traffic in another interface or almost another VLAN and use 10 Gb or more for this traffic, You should keep in mind that modern SSDs have a very high transfer rate and need a network to match this...
-
gurubert reacted to Eduardo Taboada's post in the thread CEPH Probleme : 2 OSD(s) have spurious read errors with Like.
Is not a critical error, blueStore has recovered the failure, and the cause can be a puntual problem with the network, or some hardware element (controller, disk) but it appears to be for a low response of these OSD. To remove the warning: ceph...
-
gurubert reacted to fweber's post in the thread 40 node prod cluster restarts when joining a new node or removing. with Like.
Hi, from a quick look, the "Retransmit" messages may be a symptom of network stability issues (e.g. lost packets, increased latency etc) that are more likely to occur if corosync shares a physical network with other traffic types -- I'd expect...
-
gurubert reacted to fba's post in the thread 40 node prod cluster restarts when joining a new node or removing. with Like.
There is some documentation available for Corosync network setup: https://pve.proxmox.com/wiki/Cluster_Manager#pvecm_cluster_network Using bonds is not advised, shared links with other traffic types are not advised too.
-
Yep, not a whole lot to say really - we have a 5 node ceph cluster (only 4 of which hold storage) and the SQL server's drives are on enterprise SSD backed ceph storage. Zero complaints about stability or performance. Couldn't see myself moving...
-
gurubert replied to the thread [SOLVED] Share ZFS Storage between Nodes.GlusterFS is basically dead.
-
ZFS is a local and not a shared storage. You can`t remotely access it across nodes. Whats possible is to replicate virtual disks between two IDENTICALLY named ZFS pools so both pools store a local copy the same data (means also losing half the...