Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-65892

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

    • 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

      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:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: