[SERVER-28938] RemoveCollectionChange::commit() should call invalidateAll() on collection cursor manager Created: 24/Apr/17 Updated: 30/Oct/23 Resolved: 26/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | Maria van Keulen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Storage 2017-05-29, Storage 2017-06-19 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
RemoveCollectionChange::commit() deletes the collection, but the collection cursor manager destructor expects all cursors to have been deleted. |
| Comments |
| Comment by Githook User [ 26/May/17 ] |
|
Author: {u'username': u'mvankeulen94', u'name': u'Maria van Keulen', u'email': u'maria@mongodb.com'}Message: |