Yes, indeed. I meant not-operational. Sorry.
So, if I understand this correctly. When we ever come in a situation that
we loose both storage connections on our hypervisor, we will have to
manually restore the connections first?
And thanx for the tip for speeding up thins :-).
Kind regards,
Koen
2014-04-02 15:14 GMT+02:00 Omer Frenkel <ofrenkel(a)redhat.com>:
----- Original Message -----
> From: "Koen Vanoppen" <vanoppen.koen(a)gmail.com>
> To: users(a)ovirt.org
> Sent: Wednesday, April 2, 2014 4:07:19 PM
> Subject: [Users] HA
>
> Dear All,
>
> Due our acceptance testing, we discovered something. (Document will
follow).
> When we disable one fiber path, no problem multipath finds it way no
pings
> are lost.
> BUT when we disabled both the fiber paths (so one of the storage domain
is
> gone on this host, but still available on the other host), vms go in
paused
> mode... He chooses a new SPM (can we speed this up?), put's the host in
> non-responsive (can we speed this up, more important) and the VM's stay
on
> Paused mode... I would expect that they would be migrated (yes, HA is
i guess you mean the host moves to not-operational (in contrast to
non-responsive)?
if so, the engine will not migrate vms that are paused to do io error,
because of data corruption risk.
to speed up you can look at the storage domain monitoring timeout:
engine-config --get StorageDomainFalureTimeoutInMinutes
> enabled) to the other host and reboot there... Any solution? We are still
> using oVirt 3.3.1 , but we are planning a upgrade to 3.4 after the easter
> holiday.
>
> Kind Regards,
>
> Koen
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>