[SERVER-42633] SetState::drop() doesn't cancel outstanding promises unless the global RSMM is shutdown Created: 05/Aug/19 Updated: 08/Jan/24 Resolved: 08/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | Benjamin Caimano (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Service Arch 2019-10-21 | ||||||||
| Participants: | |||||||||
| Description |
|
SetState::drop() reset's the current scan, then calls notify(true), but that doesn't actually do the work of failing promises in _waiters. Or rather, it only does that work assuming the rsm manager is shutdown. Instead it should check for if that particular RSM is removed |
| Comments |
| Comment by Benjamin Caimano (Inactive) [ 08/Oct/19 ] |
|
mira.carey@mongodb.com ended up fixing this the day after he filed it! |