Add maxTimeMSOpOnly to network message if it is a hedge sent through async_rpc API

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • Fully Compatible
    • Service Arch 2023-02-20, Service Arch 2023-03-06, Service Arch 2023-03-20, Service Arch 2023-04-03, Service Arch 2023-04-17, Service Arch 2023-05-01, Service Arch 2023-05-15, Service Arch 2023-05-29
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The 'hedges' of an operation should have a maxTimeMSOpOnly expiration attached to them to prevent overload by executing a resource intensive/long running operation on multiple machines. See https://jira.mongodb.org/browse/SERVER-46472  for the original motivation, and https://jira.mongodb.org/browse/SERVER-47117 for why it needs to be maxTimeMSOpOnly instead of the ordinary maxTimeMS. We need to ensure the async API adds this to it's own hedges. 

            Assignee:
            Alex Li
            Reporter:
            George Wangensteen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: