[SERVER-41851] Expedited scans in the RSM can continue after timeout Created: 20/Jun/19 Updated: 29/Oct/23 Resolved: 24/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | Benjamin Caimano (Inactive) |
| 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: | Service Arch 2019-07-15, Service Arch 2019-08-12 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 16 | ||||||||||||
| Description |
|
We cancel the scheduled refresh scan when we begin expedited scans here. However, we do not cancel the scheduled refresh scan when we finish the expedited scan. This means we actually start a new scan immediately after finishing an expedited scan. I think we can fix this and in the process smooth out the scheduleRefresh loop. |
| Comments |
| Comment by Githook User [ 24/Jul/19 ] |
|
Author: {'name': 'Ben Caimano', 'email': 'ben.caimano@10gen.com'}Message: |