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

Callers of getLocalOplogCollection do double locking

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication
    • ALL

    Description

      During code inspection I noticed that getLocalOplogCollection acquires DB + collection locks and then the two callers in oplog.cpp also acquire these locks.

      This should be changed so that locks are acquired only once.

      Also, getLocalOplogCollection uses OldClientContext with the shard version check set to true (default argument). This is probably not correct either.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: