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

Sharding minOpTime info writes should not wait for read concern while holding a lock

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.2.0-rc1
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding B (10/30/15)

    Description

      Waiting for write concern while holding a lock opens up opportunities for stalling replication heartbeats and for deadlocks involving the local database.

      Attachments

        Activity

          People

            kaloian.manassiev@mongodb.com Kaloian Manassiev
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: