Enhance locks for create from volume/snapshot
Currently we protects create from volume/snapshot by using a lockfile to protect the operation from concurrent deletes the volumes/snapshot used in the create operation, but we use exclusive locks on both delete and create side which will result in only one create operations from the same volume/sanpshot can process on the same time.
Proposed change:
add exclusive(write) locks for delete operations and shared(read) locks for create operations, so we can create from volume/sanpshot on parallel and also protect create operations from concurrent delete the source volume/snapshot.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- Zhenguo Niu
- Direction:
- Needs approval
- Assignee:
- Zhenguo Niu
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Eric Harney
Related branches
Related bugs
Sprints
Whiteboard
Please submit a spec to allow discussion and more details on what you are planning.
Obsoleted in favor of https:/
