[SERVER-23134] Add FetcherWithRetries Created: 14/Mar/16 Updated: 25/Jan/17 Resolved: 16/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.8 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Repl 13 (04/22/16), Repl 14 (05/13/16), Repl 15 (06/03/16) | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
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:
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. |
| Comments |
| Comment by Githook User [ 16/May/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 06/May/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |