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

Commands that don't currently take any LockManager locks must not accept afterClusterTime

    • Type: Icon: Question Question
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc2
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-11-13

      Commands such as currentOp and ping are explicitly intended not to take any LockManager locks; however, they may end up acquiring LockManager locks as part of acquiring a MODE_IS lock on the oplog when afterClusterTime is specified in the readConcern object. I think it would be worth considering have the server reject these commands when an afterClusterTime is specified to preserve this intent.

            Assignee:
            misha.tyulenev@mongodb.com Misha Tyulenev (Inactive)
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: