[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724650#comment-13724650
 ] 

edison su commented on CLOUDSTACK-3535:
---------------------------------------

It's a known issue for KVM HA.
If the kvm agent is been shutdown normally(either through "shutdown/reboot" 
command on kvm host, or "service cloudstack-agent stop"), HA will not been 
triggered. The reason is that, mgt server maintains a map of agents in memory, 
if the agent A is shutdown normally, the agent will send a shutdown request to 
mgt server, then the agent will be removed from the map. Then later on, mgt 
server's HA process will check the map, to find out any host doesn't send 
heartbeat message to mgt server for a while, unfortunately, the host A is not 
in the map any more, so HA will not happened for host A.
While, if the agent is been shutdown abruptly(such as plug-off the power), or 
the communication between agent and mgt server is broken, mgt server still has 
the agent in the map, then HA process will be triggered for that host.
                
> No HA actions are performed when a KVM host goes offline
> --------------------------------------------------------
>
>                 Key: CLOUDSTACK-3535
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Hypervisor Controller, KVM, Management Server
>    Affects Versions: 4.1.0, 4.1.1, 4.2.0
>         Environment: KVM (CentOS 6.3) with CloudStack 4.1
>            Reporter: Paul Angus
>            Priority: Blocker
>         Attachments: management-server.log.Agent
>
>
> If a KVM host 'goes down', CloudStack does not perform HA for instances which 
> are marked as HA enabled on that host (including system VMs)
> CloudStack does not show the host as disconnected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to