Recent content by brucexx

  1. B

    corosync entries in journalctl link: 0 is down etc.

    Thank you. Yes, we are using 802.3ad bond and are aware of the "fast" option. I am not encouraging nor discouraging people to use bonds (however we used them successfully for years now) but rather wanted to make people aware of the grounding issues in context of a datacenter cabinet which was...
  2. B

    corosync entries in journalctl link: 0 is down etc.

    Another update perhaps some find it useful. We are still on bonded interfaces , since last update we did not see any "link down" but we saw some retransmits almost every day , sometime more sometimes less. It never escalated to "link down" and reset but it it was something we wanted to address...
  3. B

    Shutting down the cluster with ceph

    one more thing, I need to remove an aging node and add a new node that is identical (hardware wise) as the 5 existing nodes. I would like to do that a week ahead of maintenance so it is one less thing to do. How much differences between packages is acceptable ? My current cluster is on...
  4. B

    Shutting down the cluster with ceph

    Any advice on powering down two clusters ? I have a 6 node closure on 8.3.1 (Enterprise repo) with 50-65 VMs pre node. Storage is a separate 5 node Proxmox cluster with Ceph same 8.3.1 version - this cluster is not running nay VMs. We have to power them down as part of a maintenance. The...
  5. B

    corosync entries in journalctl link: 0 is down etc.

    Update: I see some retransmits sometimes daily 1-2-3 on one or two nodes on others nothing. Sometimes it is happing daily and sometimes no corosync logs for 5 months. I actually have another cluster on that subnet (different cluster name) same version with 5 nodes configured with LACP...
  6. B

    corosync entries in journalctl link: 0 is down etc.

    I get the misalignment of the time links being down but the time frames before node fenced and after node joined are telling. Since February when we had ecc ram issue I do not see any corosync entries for "link down" and since node joined yesterday and its been 18 hours. I will try to do some...
  7. B

    corosync entries in journalctl link: 0 is down etc.

    We had a node 5 in a 6 node cluster fenced due to excessive ram ecc errors. HA worked great and all vms started on other nodes. The cluster worked with no corosync issues for last year since it was put it in production (we had ecc errors in February but ram was replaced). I should mention that...
  8. B

    3 node cluster with nodes in two diferent server rooms

    Thank you for your advice. IINerd , it is going to be a similar setup but with replication on Proxmox.
  9. B

    3 node cluster with nodes in two diferent server rooms

    Does anybody have any experience with putting cluster nodes in different server rooms ? I have several buildings and was wondering what is acceptable latency for a cluster to operate without any issues. The buildings are connected via 10Gbps fiber and latency is very low 1-2 ms. What is max...
  10. B

    pvestatd keeps restarting

    I see in that the pvestatd keeps restarting itself. I have 3 servers in 6 server cluster showing that log. See example below: pvestatd[2352]: restarting server after 72 cycles to reduce memory usage Everything seems to be working properly. How do we troubleshoot it or stop it ? Thank you...
  11. B

    Pooling local backup between two PBSs from the same datastore

    The scenario I have is with 2 Proxmox Backup servers doing sync between each other. There are no naming conflicts. In one location there is one naming convention in the other there is different one. When I pull the backups I just want to backup the the VM that are not on the other side. I just...
  12. B

    Pooling local backup between two PBSs from the same datastore

    I have two locations and backup to PBS in each location. Is it possible to sync between locations only VMs that are local to that PBS but using the same datastore ? In other words sync between locations but only VMs that are not in the other PBS datastore ? Thank you
  13. B

    Using auto scaler for the first time

    So I set it back to "on" from "warn" and now the warning of "too many pgs per old" disappeared with Health status being OK. The number of pgs is still showing 2048. Is this because of what you wrote in the first post: "The autoscaler will only start changing the pg_num automatically if the...
  14. B

    Using auto scaler for the first time

    Thank you again. I did not think about that: If you have a replicated pool with a size of 3, you will have pg_num * 3 replicas in total. 30 OSDs and with ~100 PGs per OSD -> 30 * 100 / 3 = 1000 -> 1024 , that makes more sense now. In other words I forgot about the * 3 replicas. fortunately...
  15. B

    Using auto scaler for the first time

    after exhaustive reading about pgs and how to calculate them , I decided to turn off the autoscaler (mainly because it can start rebalancing during the business hours) , I set the pgs to 2048 (was tempted to use 4096 per the 100pgs per ssd) . I have enough resources CPU/RAM to handle the OSDs...