`Shard::runCommandWithFixedRetryAttempts` must not ignore OperationContext's deadline

XMLWordPrintableJSON

    • Cluster Scalability
    • Minor Change
    • ALL
    • Sharding EMEA 2022-05-16, Sharding NYC 2023-06-26, Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07, Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16
    • 164
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The deadline is set to Milliseconds::max and the timeout from the operation context is only checked before performing network requests , meaning that the timeout is not respected in case the network request hangs or requires too long.

              Assignee:
              [DO NOT USE] Backlog - Cluster Scalability
              Reporter:
              Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: