-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Networking, Replication
-
None
-
Replication
On ExceededTimeLimit errors in the getMore callback of the OplogFetcher, we potentially still want to apply the metadata even on failure. Currently the QueryResponseStatus is a statusWith, which cannot both return the status and a value that includes metadata.
- is depended on by
-
SERVER-24088 oplog fetcher should retry on getMore ExceededTimeLimit
- Closed
- is related to
-
SERVER-23222 Replset metadata is not attached to command response on the exception path
- Closed
-
SERVER-24067 TaskExecutor RemoteCommandCallbackArgs should include elapsedMS and metadata
- Closed