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

Avoid upgrading locks in db unit tests

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Execution NAMER
    • Fully Compatible
    • Execution Team 2023-03-06, Execution Team 2023-04-03, Execution Team 2023-05-01, Execution Team 2023-05-29, Execution Team 2023-06-12, Execution NAMR Team 2023-09-04, Execution NAMR Team 2023-09-18

      Specifically:
      db_s_shard_server_test, db_repl_test, db_concurrency_test, db_unittest_test, db_catalog_test

      I took a look at the first test and we acquire an IX lock on the collection and then upgrade to a MODE_X lock in "_setFilteringMetadataByUUID". We can acquire the MODE_X lock right away and avoid the upgrade. I assume that the other unit tests will take a similar approach to avoid upgrading locks so I'm lumping them together.

            Assignee:
            gregory.noma@mongodb.com Gregory Noma
            Reporter:
            fausto.leyva@mongodb.com Fausto Leyva (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: