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

maxTimeMS on find caps getMore execution time for tailable non-awaitData cursors

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • ALL

      Running a find command with maxTimeMS that creates a tailable, non-awaitData cursor will set a limit on the server-side execution time for future getMore requests. This gist shows a series of find and getMore commands to reproduce the issue: https://gist.github.com/kevinAlbs/34e377d226a0394d016de436bfe829ef. The initial find command is run against a non-empty capped collection. Note that this is probably also an issue for aggregate.

      CC kevin.albertson bernard.gorman

            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            divjot.arora@mongodb.com Divjot Arora (Inactive)
            0 Vote for this issue
            4 Start watching this issue