Scope of image volume cache lock is too broad
Bug #1758414 reported by
Alan Bishop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Alan Bishop |
Bug Description
A synchronization lock was added to fix a problem that allowed multiple redundant entries in the image volume cache [1],[2].
[1] https:/
[2] https:/
Unfortunately, the scope of the lock is too broad and impacts performance in a couple of scenarios.
1) When the cache is not enabled, simultaneous attempts to download the image from glance are serialized.
2) Even when the volume image is cached, simultaneous requests to create a volume from the image are serialized.
The scope of the lock needs to be reduced to only serialize the portion of the process that results in an entry being added to the cache.
Changed in cinder: | |
assignee: | nobody → Alan Bishop (alan-bishop) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/556607
Review: https:/