Callers of getLocalOplogCollection do double locking

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: