Improve reshardCollection Retry Logic

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ALL
    • ClusterScalability Oct27-Nov10
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In BF-40053, reshardCollection exhausted its retries when calling _shardsvrReshardCollection here, leading to a FailedToSatisfyReadPreference error being returned to the client and ultimately failing timeseries_reshard_with_inserts.js.

      There's nothing special about this test; it has always been the case that reshardCollection can fail in this way. We should consider making either reshardCollection or its callers retry on certain error codes.

            Assignee:
            Brett Nawrocki
            Reporter:
            Brett Nawrocki
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: