cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-5485) Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only 5 of them being processed actively at the same time.
Date Fri, 10 Jan 2014 22:18:50 GMT

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

Animesh Chaturvedi updated CLOUDSTACK-5485:
-------------------------------------------

    Fix Version/s:     (was: 4.3.0)
                   4.4.0

> Vmware - Whe 10 hourly snapshots are scheduled at the same time , we see only 5 of them
being processed actively at the same time. 
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5485
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5485
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>         Environment: Build from 4.3
>            Reporter: Sangeetha Hariharan
>            Assignee: Abhinandan Prateek
>            Priority: Critical
>             Fix For: 4.4.0
>
>         Attachments: vmware.rar
>
>
> Vmware - When 10 hourly snapshots are scheduled at the same time , we see only 5 of them
being processed actively at the same time.
> Set up :
> Advanced Zone with 2 5.1 ESXI hosts.
> Steps to reproduce the problem:
> 1. Deploy 5 Vms in each of the hosts , so we start with 10 Vms.
> 2. Start concurrent snapshots for ROOT volumes of all the Vms.
> Noticed that on the Vsphere client , only 5 of these snapshots gets executed in parallel.Rest
of them get picked up when the current  snapshot jobs complete.
> Why cant we do more than 5 parallel tasks ?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message