Use shard provided functions to implement retry logic in ShardingCatalogClientImpl::insertConfigDocument

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Workload Resilience
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This function makes use of kNoRetry as the retry policy to instead perform retries manually. This is wrong since it will lead to unobservable retries, and backoff is not implemented there.

      We should instead use functions from the shard objects in order to call runBatchWriteCommand with proper retries, and write a custom predicate to evaluate if a retry should happen.

            Assignee:
            Unassigned
            Reporter:
            Guillaume Racicot
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: