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

Don't signal oplog waiters under ReplicationCoordinator mutex

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication

      Something I noticed while analyzing work done under the ReplicationCoordinator mutex is that we signal all tailable oplog waiters while advancing the committed snapshot, which seems unnecessary and costly to do while holding the mutex. The CappedInsertNotifier already has its own mutex.

            Assignee:
            Unassigned Unassigned
            Reporter:
            louis.williams@mongodb.com Louis Williams
            Votes:
            1 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: