[SERVER-17416] Deadlock between MMAP V1 journal lock and oplog collection lock Created: 27/Feb/15 Updated: 19/Sep/15 Resolved: 03/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, MMAPv1, Storage |
| Affects Version/s: | 3.0.0-rc11 |
| Fix Version/s: | 3.0.1, 3.1.0 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Participants: |
| Description |
|
It is possible to construct sequence of concurrent operations on multiple database in MMAP V1, which would result in deadlock, which is unresolvable by our current deadlock handling code. The deadlock cycle is below and the thread stacks are attached.
|
| Comments |
| Comment by Githook User [ 04/Mar/15 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Also improve the reporting of the Locker::dump function. (cherry picked from commit 197cdebe7de9be23906c175b31f056c0351e9eb3) Conflicts: |
| Comment by Githook User [ 03/Mar/15 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: Also improve the reporting of the Locker::dump function. |