[
https://issues.apache.org/jira/browse/CLOUDSTACK-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13762780#comment-13762780
]
Koushik Das commented on CLOUDSTACK-4636:
-----------------------------------------
Direct agent scan task runs at regular intervals (direct.agent.scan.interval
defaulted to 90 secs) and identifies hosts that needs to be processed for
connect. In a normal scenario (small number of hosts) hosts get connected
within that interval and there are no issues. But if due to some reason the
connect process takes more time and is not completed by the time next agent
scan runs. In this case, based on the db. state same hosts may get picked up
again. And then there will be situations where more than one thread is
processing connect for the same host.
> 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
