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

Rework dbtest's WriteContextForTests to not hold locks for its lifetime

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      WriteContextForTests holds DB and collections locks for its lifetime. This should not be needed, as the way. for query code to acquire catalog resources and locks should be through the ShardRole API. However, many of the dbtests rely on WriteContextForTests holding locks because they later run DDL functions that require the locks to be held.

            Assignee:
            Unassigned Unassigned
            Reporter:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: