Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    A
    @rzr Always a reboot after big updates, as instructed/required.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    olivierlambertO
    Hi, In that case, the easiest thing to do is: wait for the master to get back or if it won't come back, to elect a slave as the new master (one CLI command to run and you are done) It's very straightforward. It shouldn't be a dreaded scenario, because as soon as you lose management, you know it and it doesn't impact the rest of your VMs. Even without HA, it's a pretty easy situation to solve. Note it shouldn't happen that often, as long as you have a documented procedure, it should be enough to deal with it.
  • 3k Topics
    28k Posts
    simonpS
    Hi, thanks for the heads-up, we will see about doing some comparison with the backups refactoring on our dev environment to check if we lost some speed and try to fix it if so. Very happy to hear that the issue is mostly resolved. We will patch this ASAP.
  • Our hyperconverged storage solution

    44 Topics
    731 Posts
    olivierlambertO
    Different use cases: Ceph is better with more hosts (at least 6 or 7 minimum) while XOSTOR is better between 3 to 7/8. We might have better Ceph support in the future for large clusters.
  • 34 Topics
    102 Posts
    B
    La remarque a été intégrée dans l'article: https://www.myprivatelab.tech/xcp_lab_v2_ha#perte-master Merci encore pour le retour.