DaanHoogland commented on issue #10367:
URL: https://github.com/apache/cloudstack/issues/10367#issuecomment-2703406590
reproduced both outputs now
I am noticing some serious changes in the
DaanHoogland commented on issue #10367:
URL: https://github.com/apache/cloudstack/issues/10367#issuecomment-2684823596
> One extra thing I noticed is that the host going to disconnected state
does not yield an alert, though I think that is worth one as well. We could
include that in this wo
DaanHoogland commented on issue #10367:
URL: https://github.com/apache/cloudstack/issues/10367#issuecomment-2684798631
@shwstppr , I tried to reproduce both with your fork-bomb method and with
boldly powering off the host. I did get HA to kick in but only one job and one
alert.
One extra
shwstppr commented on issue #10367:
URL: https://github.com/apache/cloudstack/issues/10367#issuecomment-2656290371
@btzq In my testing with 2x KVM hosts and limited VMs, it didn't fail HA for
those VMs.
Fixing this should help the performance of HA in my opinion as it would
spend les
btzq commented on issue #10367:
URL: https://github.com/apache/cloudstack/issues/10367#issuecomment-2654030164
We actually face this alot too! Ive noticed this but wasnt sure if this was
normal.
In your test, does CS creating multiple jobs also reduce the likelihood of a
sucessful HA
shwstppr opened a new issue, #10367:
URL: https://github.com/apache/cloudstack/issues/10367
### problem
HA jobs for VM on host disconnection/down are not synchronized. CloudStack
creates multiple HA jobs for the same VM when host goes into the Down state
### versions
4.1
