-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
ALL
-
0
Currently if a getMore fails with an ExceededTimeLimit error, such as if there is no data to return, the fetcher will shutdown, and the fetcher will then look for a new sync source.
We should fix this so that if a getMore in the fetcher fails with this error, we issue a new getMore instead. We need to make sure we get and process the metadata as well. So further work will need to be done to return the metadata with the QueryResponseStatus, and then update the server with that metadata as we do on successful getMores.
- depends on
-
SERVER-24113 OplogFetcher getMore callback QueryResponseStatus should include metadata on error
- Closed
- related to
-
SERVER-23222 Replset metadata is not attached to command response on the exception path
- Closed
-
SERVER-25702 add support to OplogFetcher for restarting oplog query
- Closed