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

Prevent DBDirectClient queries from storing MaxTimeMS on cursors

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.7, 3.5.9
    • Affects Version/s: None
    • Component/s: Internal Client
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Platforms 2017-05-29, Platforms 2017-06-19

      For sanity's sake, MaxTimeMS is not allowed to be used on queries and getmores performed by DBDirectClients. However, cursors and OperationContexts both store their own representations of when they should timeout. Queries store the OperationContext's timeout on themselves as they finish. This means that a getmore performed inside a DBDirectClient may see the OperationContext's timeout and believe the MaxTimeMS was directly provided to it, and fail.

      We can assume that all operations performed by a DBDirectClient will occur inside the same OperationContext. Because DBDirectClient cursors will never cross OperationContexts, we can keep the original timeout on the OperationContext, and never transfer it to the cursor, allowing the getmore to succeed.

            spencer.jackson@mongodb.com Spencer Jackson
            spencer.jackson@mongodb.com Spencer Jackson
            0 Vote for this issue
            3 Start watching this issue