On Mon, Mar 18, 2019 at 4:15 PM levin wrote:
>
> Hi Sahina,
>
> My cluster did not enabled fencing, is somewhere I can disable restart policy
> from vdsm completely? So I can observe this case next time, and giving a fist
> investigation on unresponsive node.
>
+Martin Perina - do you know if
Hi Sahina,
My cluster did not enabled fencing, is somewhere I can disable restart policy
from vdsm completely? So I can observe this case next time, and giving a fist
investigation on unresponsive node.
Regards,
Levin
On 18/3/2019, 17:40, "Sahina Bose" wrote:
On Sun, Mar 17, 2019 at
On Sun, Mar 17, 2019 at 12:56 PM wrote:
>
> Hi, I had experience two time of 3-node hyper-converged 4.2.8 ovirt cluster
> total outage due to vdsm reactivate the unresponsive node, and cause the
> multiple glusterfs daemon restart. As a result, all VM was paused and some of
> disk image was
3 matches
Mail list logo