[SERVER-17175] $isolated updates and deletes need X lock not IX Created: 04/Feb/15 Updated: 18/Sep/15 Resolved: 13/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.0-rc9, 3.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Participants: |
| Comments |
| Comment by Githook User [ 15/Feb/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: (cherry picked from commit 7286fb36c36daaa8ee4941fa5f6c225b0a25dc61) |
| Comment by Githook User [ 13/Feb/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: |
| Comment by Mathias Stearn [ 04/Feb/15 ] |
|
scotthernandez For MMAPv1 and any other non-doc-locking engine, all IX locks on collections are already promoted to X so this would have no effect on them. |
| Comment by Scott Hernandez (Inactive) [ 04/Feb/15 ] |
|
I'm not sure this is need for mmapv1 since the yielding policy doesn't allow yielding once a document is written, and it already takes the collection lock. For docLevelLocking this does seem like an issue that needs to be addressed. |