[
https://issues.apache.org/jira/browse/CLOUDSTACK-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705519#comment-13705519
]
ASF subversion and git services commented on CLOUDSTACK-3441:
-------------------------------------------------------------
Commit e3e8bfce16f36c1aca1e706725aafab53f1c795c in branch refs/heads/master
from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e3e8bfc ]
CLOUDSTACK-3441: [Load Test] High delays between VM being allocated to Pod and
network implementation causing delays in VM deployment
This is a regresion caused due to fix for CLOUDSTACK-70. In order to fix
network restart scenario, delays got introduced in the user VM deployment
scenario.
Fixed it by separating out the network restart and new VM deployment scenario
such that the latter is not affected due to the fix for CLOUDSTACK-70.
> [Load Test] High delays between VM being allocated to Pod and network
> implementation causing delays in VM deployment
> --------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3441
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3441
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Network Controller
> Affects Versions: 4.2.0
> Environment: Load test, with simulator setup
> Reporter: Sowmya Krishnan
> Assignee: Koushik Das
> Fix For: 4.2.0
>
> Attachments: job-3014_5mins
>
>
> Scale Test set up with 20K simulated hosts, 20K VMs, basic zone, 3
> Management servers
> Also using security groups, ~5K VMs are deployed in every Security group.
> While deployment of simulator VMs, following is observed after around 4K VMs:
> There's delay between VM being allocated to Pod and network implementation
> causing delays in VM deployment. Following are the logs:
> 2013-06-10 15:51:01,215 DEBUG [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-1004:job-3014) VM is being created in podId: 1390
> 2013-06-10 15:55:31,494 DEBUG [cloud.network.NetworkManagerImpl]
> (Job-Executor-1004:job-3014) Lock is acquired for network id 204 as a part of
> network implement
> This causes delay in VM deployment and the async job to complete. The delays
> get higher and higher as more and more VMs are deployed causing an
> unacceptable delay for huge deployments, viz, > 15-20K VMs
--
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
