-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 13 (04/22/16), Repl 14 (05/13/16), Repl 15 (06/03/16)
We should add a new fetcher descendent which knows how to retry a number of times, and limited by elapsed time for the total number of retries.
This class should also know which errors exit the retry loop, using one of these strategies:
- Retry until ErrorCodeSet contains the error
- Retry while ErrorCodeSet contains the error
(where the ErrorCodeSet is provided by the caller/user)
This will be needed by the new DataReplicator/InitialSync code but can also be used by sharding use of the QueryFetcher which already has its own retry loop.
- is related to
-
SERVER-23647 Create helper function for encapsulating retry logic when talking to shards
- Closed
- related to
-
SERVER-24067 TaskExecutor RemoteCommandCallbackArgs should include elapsedMS and metadata
- Closed