Multi-lock not operating correctly when multiple threads
Bug #1371814 reported by
Joshua Harlow
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
taskflow |
Fix Released
|
High
|
Joshua Harlow | ||
0.5 |
New
|
Undecided
|
Unassigned |
Bug Description
When there are multiple threads *using the same multilock object* it appears the multilock is being to conservative and aborting to early when a lock has already been acquired by another thread (instead of waiting for acquisition to proceed). This will result in the multilock code throwing 'Lock %s not previously released' and then doing releasing of locks that the thread actually doesn't own. This is undesirable and not the expected behavior when these types of objects are shared among > 1 thread.
Changed in taskflow: | |
importance: | Undecided → Critical |
assignee: | nobody → Joshua Harlow (harlowja) |
Changed in taskflow: | |
status: | New → Confirmed |
summary: |
- Multlock not operating correctly when multiple threads + Multi-lock not operating correctly when multiple threads |
description: | updated |
Changed in taskflow: | |
milestone: | next-juno → next-kilo |
Changed in taskflow: | |
status: | Fix Committed → Fix Released |
Changed in taskflow: | |
milestone: | next-kilo → none |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/122887
Review: https:/