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

QueryStageCollectionScanTest acquires global IX lock and then calls AutoGetCollectionForRead

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Execution Team 2023-04-17, Execution Team 2023-05-01, Execution Team 2023-05-15

      After acquiring the IX lock on the collection level we can use AutoGetCollection instead of AutoGetCollectionForRead: https://github.com/10gen/mongo/blob/c8f6bd7b917856060fdfb2d78dab17b734fc4848/src/mongo/dbtests/query_stage_collscan.cpp#L777-L778

      AutoGetCollectionForRead acquires an IS lock which should be covered under the IX lock but oddly enough I ran into an issue with upgrading locks. Could be due to the way I was prohibiting lock upgrades described in SERVER-73040.

            Assignee:
            fausto.leyva@mongodb.com Fausto Leyva (Inactive)
            Reporter:
            fausto.leyva@mongodb.com Fausto Leyva (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: