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

MaxTimeMSExpired returned on getMore command that follows HedgedReads find

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc3, 4.7.0
    • Affects Version/s: None
    • Component/s: Internal Code
    • Labels:
    • Fully Compatible
    • ALL
    • v4.4
    • Service Arch 2020-04-06, Service arch 2020-04-20
    • 36

      When a find command is hedged it adds a MaxTimeMS to the hedged request to avoid wasting resources on a long-running queries.
      While NetworkInteface ignores the MaxTimeMSExpired error for hedged finds , it can not do so for getMore because this is a separate command and is not hedged.
      However if there is a getMore followed the find it will inherit the leftover of MaxTimeMS, and will error when it expired.
      This is a bug as the result depends on if it was run via hedged or non hedged path.

            misha.tyulenev@mongodb.com Misha Tyulenev
            misha.tyulenev@mongodb.com Misha Tyulenev
            0 Vote for this issue
            5 Start watching this issue