[SERVER-21413] Unify the config server and shard network calls' retrying logic Created: 11/Nov/15 Updated: 09/Jul/16 Resolved: 09/Jul/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Misha Tyulenev |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Currently, the network call retrying logic for NotMaster and network error is scattered across multiple components - replica set monitor, shard registry, catalog manager and the async results merger. We should come up with a comprehensive solution, which unifies the retries that we do in all these places. |