[
https://issues.apache.org/jira/browse/CLOUDSTACK-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778919#comment-13778919
]
ilya musayev commented on CLOUDSTACK-4636:
------------------------------------------
Hi Koushik,
I've opened a similar ticket, except in my case it also affects 4.1.1
https://issues.apache.org/jira/browse/CLOUDSTACK-4740
I've looked at the patch and it seems like something i could re-use in 4.1 code
base.
Please let me know if you see any issues
Thanks
ilya
> 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
