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

maxTimeMS on an instance/database level

    XMLWordPrintable

    Details

    • Case:

      Description

      MongoDB 2.6 introduced the .maxTimeMS() cursor method, which allows you to specify a max running time for each query. This is awesome for ad-hoc queries, but I wondered if there was a way to set this value on a per-instance or per-database (or even per-collection) level, to try and prevent locking in general.

      And if so, could that value then be OVERWRITTEN on a per-query basis? I would love to set an instance level timeout of 3000ms or thereabouts (since that would be a pretty extreme running time for queries issued by my application), but then be able to ignore it if I had a report to run.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-query Backlog - Query Team
            Reporter:
            fordjp Jason Ford
            Participants:
            Votes:
            10 Vote for this issue
            Watchers:
            20 Start watching this issue

              Dates

              Created:
              Updated: