Consider WriteConcernTimeout as retriable on shard remote calls on idempotent operations

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      Based on the investigation of SERVER-108481 we should make Shard::remoteIsRetriableError handle the retry on WriteConcernTimeout the same as Shard::localIsRetriableError (eg mark WriteConcernTimeout retryable)

            Assignee:
            Unassigned
            Reporter:
            Wolfee Farkas
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: