You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Koushik Das (JIRA)" <ji...@apache.org> on 2013/09/10 07:50:52 UTC

[jira] [Commented] (CLOUDSTACK-4636) All Vm's in a cluster were stopped and/or started after management server restart

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

Koushik Das commented on CLOUDSTACK-4636:
-----------------------------------------

This is not seen in a normal setup but only in a scaled up setup (> 1K host) when the MS is under a high load.
                
> All Vm's in a cluster were stopped and/or started after management server restart
> ---------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4636
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4636
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: XS cluster
>            Reporter: Koushik Das
>            Assignee: Koushik Das
>             Fix For: 4.2.1
>
>
> Issue happens as there are more than one thread processing connect for a host simultaneously during MS restart. The VM full sync. logic is not designed to work in this scenario and as a result user VMs may get stopped incorrectly.

--
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