[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:
Depends
is depended on by SERVER-42340 ReplicaSetMonitor throws to the top o... Closed
Related
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: SERVER-41851 Expedited scans in the RSM no longer continue after timeout
Branch: master
https://github.com/mongodb/mongo/commit/f4e4fab36f9ee654def954465086151b41a1aa8e

Generated at Thu Feb 08 04:58:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.