I’m aware of the heal process but it’s unclear to me if the update continues to run while the volumes are healing and resumes when they are done. There doesn’t seem to be any indication in the ui (unless I’m mistaken)

On Tue, Aug 6, 2019 at 6:06 PM Robert O'Kane <okane@khm.de> wrote:

Hello,

Often(?), updates to a hypervisor that also has (provides) a Gluster
brick takes the hypervisor offline (updates often require a reboot).

This reboot then makes the brick "out of sync" and it has to be resync'd.

I find it a "feature" than another host that is also part of a gluster
domain can not be updated (rebooted) before all the bricks are updated
in order to guarantee there is not data loss. It is called Quorum, or?

Always let the heal process end. Then the next update can start.
For me there is ALWAYS a healing time before Gluster is happy again.

Cheers,

Robert O'Kane


Am 06.08.2019 um 16:38 schrieb Shani Leviim:
> Hi Jayme,
> I can't recall such a healing time.
> Can you please retry and attach the engine & vdsm logs so we'll be smarter?
>
> *Regards,
> *
> *Shani Leviim
> *
>
>
> On Tue, Aug 6, 2019 at 5:24 PM Jayme <jaymef@gmail.com
> <mailto:jaymef@gmail.com>> wrote:
>
>     I've yet to have cluster upgrade finish updating my three host HCI
>     cluster.  The most recent try was today moving from oVirt 4.3.3 to
>     4.3.5.5.  The first host updates normally, but when it moves on to
>     the second host it fails to put it in maintenance and the cluster
>     upgrade stops.
>
>     I suspect this is due to that fact that after my hosts are updated
>     it takes 10 minutes or more for all volumes to sync/heal.  I have
>     2Tb SSDs.
>
>     Does the cluster upgrade process take heal time in to account before
>     attempting to place the next host in maintenance to upgrade it? Or
>     is there something else that may be at fault here, or perhaps a
>     reason why the heal process takes 10 minutes after reboot to complete?
>     _______________________________________________
>     Users mailing list -- users@ovirt.org <mailto:users@ovirt.org>
>     To unsubscribe send an email to users-leave@ovirt.org
>     <mailto:users-leave@ovirt.org>
>     Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>     oVirt Code of Conduct:
>     https://www.ovirt.org/community/about/community-guidelines/
>     List Archives:
>     https://lists.ovirt.org/archives/list/users@ovirt.org/message/5XM3QB3364ZYIPAKY4KTTOSJZMCWHUPD/
>
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/GBX3L23MWGMTF7Q4KGVR63RIQZFYXGWK/
>

--
Systems Administrator
Kunsthochschule für Medien Köln
Peter-Welter-Platz 2
50676 Köln
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OBAHFFFTDOI7LHAH5AVI5OPUQUQTABWM/

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/T27ROHWZPJL475HBHTFDGRBSYHJMWYDR/