cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koushik Das (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-4636) In a scaled up setup all Vm's in a cluster were stopped and/or started after management server restart
Date Tue, 10 Sep 2013 06:02:51 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Koushik Das updated CLOUDSTACK-4636:
------------------------------------

    Summary: In a scaled up setup all Vm's in a cluster were stopped and/or started after
management server restart  (was: All Vm's in a cluster were stopped and/or started after management
server restart)
    
> In a scaled up setup 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

Mime
View raw message