cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3441) [Load Test] High delays between VM being allocated to Pod and network implementation causing delays in VM deployment
Date Wed, 21 Aug 2013 09:57:51 GMT

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

ASF subversion and git services commented on CLOUDSTACK-3441:
-------------------------------------------------------------

Commit 502c1db1030cfa01850127ba8a8e5e7b1eaf8ead in branch refs/heads/master from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=502c1db ]

CLOUDSTACK-3441: [Load Test] High delays between VM being allocated to Pod and network implementation
causing delays in VM deployment
The locking code in implement/shutdown network code was not efficient. Even in order to check
the current state of the network lock was getting acquired which is not required. This resulted
in delays in deploy VM as can be seen from attached logs where the code waited on the lock
just to check if network is implemented.
As part of the fix moved out code that is checking if the network is already implemented or
shutdowned outside the lock.

                
> [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
>            Priority: Critical
>             Fix For: Future
>
>         Attachments: job1792.log, 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

Mime
View raw message