Repository navigation
Delay in determining a KVM host is down #10477
Description
problem
With the default configurations, CloudStack determines a KVM host is down in 15-20 minutes. The HA-enabled instances will be started on another host only after this process. While reviewing the delay for the host state investigation followed by a ping timeout I see one command that takes 10 minutes 'com.cloud.agent.api.CheckOnHostCommand printing in the logs the following message 'timed out after 3600'. Later the host is determined as down via the neighbouring host quickly.
I suspect there is some issue in this specific implementation and if fixed the VM HA delay in KVM could be reduced by 10 minutes.
2025-01-28 06:22:30,041 DEBUG [c.c.a.t.Request] (AgentTaskPool-4:ctx-1ece8add) (logid:49d74f9a) Seq 2-4979573812988215360: Sending { Cmd , MgmtId: 32988184186020, via: 2(ref-trl-5786-k-Mu22-jithin-raju-kvm2), Ver: v1, Flags: 100011, [{"com.cloud.agent.api.CheckOnHostCommand":{"host":{"guid":"439751ba-a6eb-3103-b60d-8321f53224fb-LibvirtComputingResource","privateNetwork":{"ip":"10.1.33.180","netmask":"255.255.240.0","mac":"1e:00:a9:00:0a:72","isSecurityGroupEnabled":"false"},"storageNetwork1":{"ip":"10.1.33.180","netmask":"255.255.240.0","mac":"1e:00:a9:00:0a:72","isSecurityGroupEnabled":"false"}},"reportCheckFailureIfOneStorageIsDown":"false","wait":"0","bypassHostMaintenance":"false"}}] }
2025-01-28 06:32:14,792 DEBUG [c.c.a.m.AgentAttache] (AgentTaskPool-4:ctx-1ece8add) (logid:49d74f9a) Seq 2-4979573812988215360: Waiting some more time because this is the current command
2025-01-28 06:32:14,792 DEBUG [c.c.a.m.AgentAttache] (AgentTaskPool-4:ctx-1ece8add) (logid:49d74f9a) Seq 2-4979573812988215360: Waiting some more time because this is the current command
2025-01-28 06:32:14,792 WARN [c.c.a.m.AgentAttache] (AgentTaskPool-4:ctx-1ece8add) (logid:49d74f9a) Seq 2-4979573812988215360: Timed out on Seq 2-4979573812988215360: { Cmd , MgmtId: 32988184186020, via: 2(ref-trl-5786-k-Mu22-jithin-raju-kvm2), Ver: v1, Flags: 100011, [{"com.cloud.agent.api.CheckOnHostCommand":{"host":{"guid":"439751ba-a6eb-3103-b60d-8321f53224fb-LibvirtComputingResource","privateNetwork":{"ip":"10.1.33.180","netmask":"255.255.240.0","mac":"1e:00:a9:00:0a:72","isSecurityGroupEnabled":"false"},"storageNetwork1":{"ip":"10.1.33.180","netmask":"255.255.240.0","mac":"1e:00:a9:00:0a:72","isSecurityGroupEnabled":"false"}},"reportCheckFailureIfOneStorageIsDown":"false","wait":"0","bypassHostMaintenance":"false"}}] }
2025-01-28 06:32:14,793 DEBUG [c.c.a.m.AgentAttache] (AgentTaskPool-4:ctx-1ece8add) (logid:49d74f9a) Seq 2-4979573812988215360: Cancelling.
2025-01-28 06:32:14,793 WARN [c.c.a.m.AgentManagerImpl] (AgentTaskPool-4:ctx-1ece8add) (logid:49d74f9a) Operation timed out: Commands 4979573812988215360 to Host 2 timed out after 3600
https://gist.github.com/rajujith/9a51c52163eb4862b497057a40e8b812#file-acs-kvm-vm-ha-host-down
versions
4.19.1.3
The steps to reproduce the bug
- Power off the host via ILO/IDRAC or power off the nested hypervisor through the base hypervisor.
- Observe the delay in VM HA and review the logs
...
What to do about it?
Reduce the delay in the VM HA on KVM.
Reacted by btzq
Activity
DaanHoogland commented on Feb 27, 2025
@rajujith , can you try with latest? There is configurable timeouts for agent commands.
rajujith commented on Mar 11, 2025
@DaanHoogland I tried in the latest and there is a significant improvement due to the default timeout of CheckOnHostCommand being set to 20 seconds resulting timeout of 40 seconds. I tried a few configurations and the results are below. I used the commands.timeout in the PR #9659 .
Default settings:About 5 minutes.
commands.timeout=CheckHealthCommand=5,CheckOnHostCommand=5: About 2 Minutes, 30 seconds.
ping.interval=30,ping.timeout=2,commands.timeout=CheckHealthCommand=5,CheckOnHostCommand=5: About 2 Minutes.
cc: @harikrishna-patnala
alsko-icom commented on Mar 20, 2025
@rajujith hi! can you elaborate a bit what are the exact settings and values you used and the steps required? (server-agent restart maybe) to implement the specified wait setting? I believe I have located it under global settings-misc-other-wait. I am facing an issue where after removing power from a cluster kvm, the VMs take 9 minutes to reboot to another node and I am trying to reduce the time.
rajujith commented on Mar 26, 2025
@alsko-icom With the latest nightly build, without making any changes, the VM HA starts about 5 minutes after a KVM host crashed. I simulated the host crash by powering off the nested KVM I used.
If you want to reduce it further, you can set the global configuration 'commands.timeout' value to a suitable value like "CheckHealthCommand=5,CheckOnHostCommand=5". I saw VM HA triggered after a host crash in 2 Minutes and 30 seconds.
Once a host crashes CloudStack should identify that the host is unreachable, that is determined by 'ping.interval * ping.timeout' [1] So reducing the value ( use an appropriate value based on your testing) will make the host crash detection faster. Then it starts multiple investigations where it uses commands like 'CheckHealthCommand' , CheckOnHostCommand and a few more. you can view the sample log file in the issue description.
Updating ping.interval,ping.timeout,commands.timeout requires a cloudstack-management service restart.
I didn't verify anything on the host HA, I tried only the VM HA.
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/High+Availability+Developer's+Guide