Alena Prokharchyk created CLOUDSTACK-304:
--------------------------------------------
Summary: Add synchronization for createSnapshot command per host
basis
Key: CLOUDSTACK-304
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-304
Project: CloudStack
Issue Type: Bug
Components: Management Server
Affects Versions: 4.0.0
Reporter: Alena Prokharchyk
Assignee: Alena Prokharchyk
Fix For: 4.1.0
With the current code for snapshots, cloudStack always creates snapshot on the
host where vm is Running (for vms in Running state) or on the host where vm
used to run the last time (for vms in Stopped state). As the commands are not
synchronized on the agent side, the case when multiple commands are send to the
backend at the same time can lead to the performance issues on the hypervisor
side. At the end there is a high possibility that createSnapshot command might
time out on the Xen side_._
The solution is to synchronize number of concurrent snapshots per host basis.
The threshold should be configurable as the customer usually knows how many
snapshots at a time the backend can handle. While the concurrent snapshots are
being processed by the backend, all subsequent snapshot commands scheduled for
execution on the same host, should wait in the queue. And the wait timeout
should also be a configurable value.
--
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
