Unify the config server and shard network calls' retrying logic

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Misha Tyulenev (Inactive)
              Reporter:
              Kaloian Manassiev
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: