[SERVER-34790] Ensure proper locks are held when doing reads or writes Created: 02/May/18 Updated: 29/Oct/23 Resolved: 25/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc1, 4.1.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | nyc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v4.0
|
||||
| Sprint: | Storage NYC 2018-06-04 | ||||
| Participants: | |||||
| Description |
|
We should check that intent exclusive (IX) locks are held for Global, the database, and the collection resources when doing writes. A similar check should be performed for reads, and/or starting a storage engine transaction. |
| Comments |
| Comment by Githook User [ 29/May/18 ] |
|
Author: {'username': 'milkie', 'name': 'Eric Milkie', 'email': 'milkie@10gen.com'}Message: (cherry picked from commit ec2b67ac05f7aaa05b990e18cd7c23109a2e6eb7) |
| Comment by Githook User [ 25/May/18 ] |
|
Author: {'username': 'milkie', 'name': 'Eric Milkie', 'email': 'milkie@10gen.com'}Message: |