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

mongod and mongos change streams treat maxTimeMS differently

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Execution

    Description

      the behavior I seemed to observe is that mongod will ignore maxTimeMS. even if its lower than maxAwaitTimeMS it won't timeout the query. but on mongos it will hit a timeout if mongod doesn't respond before maxTimeMS. in the spirit of reducing behavior differences between replSets and sharded clusters we should fix this to have just one behavior. I tested this with 7.1 sharded/unsharded and 5.0 sharded/unsharded. and it seems 7.1 was the only one where it errored

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            mickey.winters@mongodb.com Mickey Winters
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: